Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
Date:   Thu, 05 May 2022 13:54:16 +0100
From:   Marc Zyngier <maz@kernel.org>
To:     Bartosz Golaszewski <brgl@bgdev.pl>
Cc:     Jon Hunter <jonathanh@nvidia.com>,
        Linus Walleij <linus.walleij@linaro.org>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        linux-tegra@vger.kernel.org
Subject: Re: [PATCH V2] gpio: max77620: Make the irqchip immutable
In-Reply-To: <CAMRc=MeXUN6P8kWxB75GsXdKD7Owz9mX5HpgfQoMGeJh-z3=Rw@mail.gmail.com>
References: <20220504144406.36744-1-jonathanh@nvidia.com>
 <CAMRc=MeXUN6P8kWxB75GsXdKD7Owz9mX5HpgfQoMGeJh-z3=Rw@mail.gmail.com>
User-Agent: Roundcube Webmail/1.4.13
Message-ID: <6629e06d06f647923c04502ce3133f76@kernel.org>
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 2022-05-05 13:42, Bartosz Golaszewski wrote:
> On Wed, May 4, 2022 at 4:44 PM Jon Hunter <jonathanh@nvidia.com> wrote:
>> 
>> Commit 6c846d026d49 ("gpio: Don't fiddle with irqchips marked as
>> immutable") added a warning to indicate if the gpiolib is altering the
>> internals of irqchips. Following this change the following warning is
>> now observed for the max77620 gpio driver ...
>> 
>>  WARNING KERN gpio gpiochip0: (max77620-gpio): not an immutable chip,
>>         please consider fixing it!
>> 
>> Fix the above warning by making the max77620 gpio driver immutable.
>> 
>> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
>> ---
> 
> Queued for fixes, thanks!

You mean fixes for *5.19*, right?

Thanks,

         M.
-- 
Jazz is not dead. It just smells funny...