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
Date: Thu, 05 May 2022 13:54:16 +0100 [thread overview]
Message-ID: <6629e06d06f647923c04502ce3133f76@kernel.org> (raw)
In-Reply-To: <CAMRc=MeXUN6P8kWxB75GsXdKD7Owz9mX5HpgfQoMGeJh-z3=Rw@mail.gmail.com>
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...
next prev parent reply other threads:[~2022-05-05 12:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 14:44 [PATCH V2] gpio: max77620: Make the irqchip immutable Jon Hunter
2022-05-04 15:01 ` Marc Zyngier
2022-05-05 12:42 ` Bartosz Golaszewski
2022-05-05 12:54 ` Marc Zyngier [this message]
2022-05-05 12:57 ` Bartosz Golaszewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6629e06d06f647923c04502ce3133f76@kernel.org \
--to=maz@kernel.org \
--cc=brgl@bgdev.pl \
--cc=jonathanh@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox