From: Romain Naour <romain.naour@smile.fr>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: netdev@vger.kernel.org, linux@armlinux.org.uk, pabeni@redhat.com,
kuba@kernel.org, edumazet@google.com, davem@davemloft.net,
f.fainelli@gmail.com, vivien.didelot@gmail.com, andrew@lunn.ch,
UNGLinuxDriver@microchip.com, woojung.huh@microchip.com,
Romain Naour <romain.naour@skf.com>,
Arun Ramadoss <arun.ramadoss@microchip.com>
Subject: Re: [PATCH v2 1/2] net: dsa: microchip: add KSZ9896 switch support
Date: Wed, 31 Aug 2022 17:43:27 +0200 [thread overview]
Message-ID: <e7ba61d7-de75-3cfe-ee92-3f234dd36289@smile.fr> (raw)
In-Reply-To: <20220831153804.mqkbw2ln6n67m6jf@skbuf>
Hi Vladimir,
Le 31/08/2022 à 17:38, Vladimir Oltean a écrit :
> Hi Romain,
>
> On Tue, Aug 30, 2022 at 09:58:59AM +0200, Romain Naour wrote:
>> It seems that the KSZ9896 support has been sent to the kernel netdev
>> mailing list a while ago but no further patch was sent after the
>> initial review:
>> https://www.spinics.net/lists/netdev/msg554771.html
>>
>> The initial testing with the ksz9896 was done on a 5.10 kernel
>> but due to recent changes in dsa microchip driver it was required
>> to rework this initial version for 6.0-rc2 kernel.
>>
>> v2: remove duplicated SoB line
>
> To be clear, was the patch also tested on net-next, or only formatted there?
The patch was runtime tested on a 6.0-rc2 kernel and a second time on a 6.0-rc3
kernel but not on net-next.
Is it ok with rc releases or do I need to test on net-next too?
Best regards,
Romain
next prev parent reply other threads:[~2022-08-31 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 7:58 [PATCH v2 1/2] net: dsa: microchip: add KSZ9896 switch support Romain Naour
2022-08-30 7:59 ` [PATCH v2 2/2] net: dsa: microchip: add KSZ9896 to KSZ9477 I2C driver Romain Naour
2022-08-31 15:38 ` [PATCH v2 1/2] net: dsa: microchip: add KSZ9896 switch support Vladimir Oltean
2022-08-31 15:43 ` Romain Naour [this message]
2022-08-31 15:51 ` Vladimir Oltean
2022-08-31 22:25 ` Romain Naour
2022-09-01 12:26 ` Vladimir Oltean
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=e7ba61d7-de75-3cfe-ee92-3f234dd36289@smile.fr \
--to=romain.naour@smile.fr \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=arun.ramadoss@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=romain.naour@skf.com \
--cc=vivien.didelot@gmail.com \
--cc=woojung.huh@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