From: <Conor.Dooley@microchip.com>
To: <Nicolas.Ferre@microchip.com>, <geert+renesas@glider.be>,
<Ludovic.Desroches@microchip.com>, <linus.walleij@linaro.org>,
<brgl@bgdev.pl>, <Horatiu.Vultur@microchip.com>,
<Kavyasree.Kotagiri@microchip.com>
Cc: <linux-gpio@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] gpio: GPIO_SAMA5D2_PIOBU should depend on ARCH_AT91
Date: Mon, 11 Jul 2022 12:08:53 +0000 [thread overview]
Message-ID: <f9cfabe3-fbec-05b1-a49b-9e31da043ce7@microchip.com> (raw)
In-Reply-To: <8dbed370-c6d6-496c-eb41-efce2ee78286@microchip.com>
On 11/07/2022 13:03, Nicolas Ferre wrote:
> On 11/07/2022 at 10:36, Geert Uytterhoeven wrote:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>
>> The SAMA5D2 PIOBU is only present on some AT91/Microchip SoCs. Hence
>> add a dependency on ARCH_AT91, to prevent asking the user about this
>> driver when configuring a kernel without AT91/Microchip SoC support.
>>
>> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
> Looks good to me:
> Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
>
> I'm adding to the thread my colleagues from lan966 and mpfs if it
> happens that they use this same IP on their SoC. Anyway, we can
> add them afterwards.
Not on FPGAs, so you're safe there!
next prev parent reply other threads:[~2022-07-11 12:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 8:36 [PATCH] gpio: GPIO_SAMA5D2_PIOBU should depend on ARCH_AT91 Geert Uytterhoeven
2022-07-11 12:03 ` Nicolas Ferre
2022-07-11 12:08 ` Conor.Dooley [this message]
2022-07-12 10:23 ` 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=f9cfabe3-fbec-05b1-a49b-9e31da043ce7@microchip.com \
--to=conor.dooley@microchip.com \
--cc=Horatiu.Vultur@microchip.com \
--cc=Kavyasree.Kotagiri@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=brgl@bgdev.pl \
--cc=geert+renesas@glider.be \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).