From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Robert Marko <robert.marko@sartura.hr>, <mturquette@baylibre.com>,
<sboyd@kernel.org>, <lee@kernel.org>,
<gregkh@linuxfoundation.org>, <jirislaby@kernel.org>,
<linux-clk@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-serial@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Cc: <luka.perkov@sartura.hr>
Subject: Re: [PATCH 2/3] mfd: at91-usart: make it selectable for ARCH_LAN969X
Date: Fri, 8 Nov 2024 14:20:29 +0100 [thread overview]
Message-ID: <743af86d-e7ad-4698-b7a4-d75cf46f00d7@microchip.com> (raw)
In-Reply-To: <20241108112355.20251-2-robert.marko@sartura.hr>
On 08/11/2024 at 12:22, Robert Marko wrote:
> LAN969x uses the AT91 USART IP so make it selectable for ARCH_LAN969X.
>
> Signed-off-by: Robert Marko <robert.marko@sartura.hr>
Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
> ---
> drivers/mfd/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
> index ae23b317a64e..f280ba28d618 100644
> --- a/drivers/mfd/Kconfig
> +++ b/drivers/mfd/Kconfig
> @@ -138,7 +138,7 @@ config MFD_AAT2870_CORE
> config MFD_AT91_USART
> tristate "AT91 USART Driver"
> select MFD_CORE
> - depends on ARCH_AT91 || COMPILE_TEST
> + depends on ARCH_AT91 || ARCH_LAN969X ||COMPILE_TEST
> help
> Select this to get support for AT91 USART IP. This is a wrapper
> over at91-usart-serial driver and usart-spi-driver. Only one function
> --
> 2.47.0
>
>
next prev parent reply other threads:[~2024-11-08 13:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 11:22 [PATCH 1/3] clk: lan966x: make it selectable for ARCH_LAN969X Robert Marko
2024-11-08 11:22 ` [PATCH 2/3] mfd: at91-usart: " Robert Marko
2024-11-08 13:20 ` Nicolas Ferre [this message]
2024-11-08 11:22 ` [PATCH 3/3] tty: serial: atmel: " Robert Marko
2024-11-08 13:25 ` Nicolas Ferre
2024-11-08 13:40 ` Robert Marko
2024-11-08 13:52 ` Nicolas Ferre
2024-11-14 20:36 ` [PATCH 1/3] clk: lan966x: " Stephen Boyd
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=743af86d-e7ad-4698-b7a4-d75cf46f00d7@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=luka.perkov@sartura.hr \
--cc=mturquette@baylibre.com \
--cc=robert.marko@sartura.hr \
--cc=sboyd@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).