From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Arnd Bergmann <arnd@arndb.de>, Michael Walle <michael@walle.cc>
Cc: Russell King <linux@armlinux.org.uk>,
Olof Johansson <olof@lixom.net>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
SoC Team <soc@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@microchip.com>,
Horatiu Vultur - M31836 <Horatiu.Vultur@microchip.com>
Subject: Re: [PATCH] ARM: configs: enable support for Kontron KSwitch D10
Date: Wed, 18 May 2022 18:00:50 +0200 [thread overview]
Message-ID: <b97221e1-dd43-e2e0-5c37-f86162768f00@microchip.com> (raw)
In-Reply-To: <CAK8P3a01B2uEP7=AkVBG5FYdfMHyReFP=120Ay3+s2EV9kO5Uw@mail.gmail.com>
Arnd, Michael,
On 18/05/2022 at 16:52, Arnd Bergmann wrote:
> On Wed, May 18, 2022 at 3:15 PM Michael Walle <michael@walle.cc> wrote:
>>
>> The Kontron KSwitch D10 is based on a Microchip LAN9668 SoC. It is a
>> managed ethernet network switch with either 8 copper ports or 6 copper
>> ports and 2 SFP cages.
>>
>> Enable all required kconfig symbols, either as module where possible or
>> compiled-in where it is not possible.
>>
>> Signed-off-by: Michael Walle <michael@walle.cc>
Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
>> ---
>> FWIW, there will be a board in our lab in KernelCI using this config.
>
> The patch looks ok to me, but normally I'd expect it to go through the
> platform maintainer tree unless there is a reason not to. Adding the at91
> maintainers to Cc here.
>
> It's also a bit late for 5.19, but if everyone agrees, I can add the patch
> to the arm/late branch.
If it's possible for you Arnd, I do agree that you take it in the
arm/late branch.
Thanks, best regards,
Nicolas
--
Nicolas Ferre
prev parent reply other threads:[~2022-05-18 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 14:15 Michael Walle
2022-05-18 14:52 ` Arnd Bergmann
2022-05-18 16:00 ` 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=b97221e1-dd43-e2e0-5c37-f86162768f00@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=Horatiu.Vultur@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=claudiu.beznea@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michael@walle.cc \
--cc=olof@lixom.net \
--cc=soc@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
all inboxes | Powered by JetHome®