From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Michael Walle <michael@walle.cc>,
Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>
Cc: <linux@armlinux.org.uk>, <linus.walleij@linaro.org>,
<alexandre.belloni@bootlin.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <UNGLinuxDriver@microchip.com>,
<Manohar.Puri@microchip.com>
Subject: Re: [PATCH v3] ARM: at91: debug: add lan966 support
Date: Fri, 13 May 2022 13:48:34 +0200 [thread overview]
Message-ID: <0868bdd4-04d5-cc7e-9f62-28e370e8ae5a@microchip.com> (raw)
In-Reply-To: <8f5c894ee9670c991e7d2897ef7c84aa@walle.cc>
On 13/05/2022 at 11:09, Michael Walle wrote:
> Am 2022-05-13 09:50, schrieb Kavyasree Kotagiri:
>> Add support for low-level debugging on FLEXCOM USART of
>> LAN966 SoC.
>>
>> Signed-off-by: Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>
Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
And queued in at91-soc for 5.19.
Thanks Kavyasree and Michael!
Regards,
Nicolas
>> ---
>> arch/arm/Kconfig.debug | 22 ++++++++++++++++++++++
>> 1 file changed, 22 insertions(+)
>>
>> diff --git a/arch/arm/Kconfig.debug b/arch/arm/Kconfig.debug
>> index 0c9497d549e3..b8a2364df9c1 100644
>> --- a/arch/arm/Kconfig.debug
>> +++ b/arch/arm/Kconfig.debug
>> @@ -210,6 +210,26 @@ choice
>> Say Y here if you want kernel low-level debugging support
>> on the FLEXCOM3 port of SAMA7G5.
>>
>> + config DEBUG_AT91_LAN966_FLEXCOM
>> + bool "Kernel low-level debugging on LAN966 FLEXCOM USART"
>> + select DEBUG_AT91_UART
>> + depends on SOC_LAN966x
>
> depends on SOC_LAN966
>
> With that fixed:
> Reviewed-by: Michael Walle <michael@walle.cc>
> Tested-by: Michael Walle <michael@walle.cc>
>
> -michael
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
Nicolas Ferre
prev parent reply other threads:[~2022-05-13 11:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 7:50 Kavyasree Kotagiri
2022-05-13 9:09 ` Michael Walle
2022-05-13 11:48 ` Nicolas Ferre [this message]
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=0868bdd4-04d5-cc7e-9f62-28e370e8ae5a@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=Manohar.Puri@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=kavyasree.kotagiri@microchip.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michael@walle.cc \
/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
all inboxes | Powered by JetHome®