From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Mark Brown <broonie@kernel.org>
Cc: Ludovic Desroches <ludovic.desroches@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@microchip.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-gpio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] pinctrl: at91: Make the irqchip immutable
Date: Tue, 7 Mar 2023 09:01:18 +0530 [thread overview]
Message-ID: <3b16b932-da02-30b4-2eae-29c26b3453a1@microchip.com> (raw)
In-Reply-To: <CACRpkdbeVw1vBikYi3RimOO8K-KKLOpO=9O_yZFBt4oORi=Wgg@mail.gmail.com>
On 06/03/2023 at 18:50, Linus Walleij wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Thu, Feb 16, 2023 at 4:49 PM Mark Brown <broonie@kernel.org> wrote:
>
>> To help gpiolib not fiddle around with the internals of the irqchip
>> flag the chip as immutable, adding the calls into the gpiolib core
>> required to do so.
>>
>> Signed-off-by: Mark Brown <broonie@kernel.org>
>
> 1) I'm impressed that you're using AT91 hardware
I'm delighted that you're using AT91 hardware ;-)
Thanks for your help Mark!
Regards,
Nicolas
> 2) Can you respin this on top of my pinctrl devel branch:
> https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git/log/?h=devel
> There are some Andy-cleanups already queued for AT91 so I am a bit
> worried of collisions. (If you feel confident they are orthogonal just
> use v6.3-rc1)
>
> Yours,
> Linus Walleij
--
Nicolas Ferre
next prev parent reply other threads:[~2023-03-07 3:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 15:43 [PATCH 0/2] pinctrl: at91: Minor cleanups Mark Brown
2023-02-16 15:43 ` [PATCH 1/2] pinctrl: at91: Make the irqchip immutable Mark Brown
2023-02-17 11:46 ` Claudiu.Beznea
2023-03-06 13:20 ` Linus Walleij
2023-03-06 13:42 ` Mark Brown
2023-03-07 3:31 ` Nicolas Ferre [this message]
2023-02-16 15:43 ` [PATCH 2/2] pinctrl: at91: Remove pioc_index from struct at91_gpio_chip Mark Brown
2023-02-17 11:47 ` Claudiu.Beznea
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=3b16b932-da02-30b4-2eae-29c26b3453a1@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=broonie@kernel.org \
--cc=claudiu.beznea@microchip.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
/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;
as well as URLs for NNTP newsgroup(s).