From: Vladimir Oltean <olteanv@gmail.com>
To: Romain Naour <romain.naour@smile.fr>
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: Thu, 1 Sep 2022 15:26:16 +0300 [thread overview]
Message-ID: <20220901122616.tbux3hp2oyej4wcq@skbuf> (raw)
In-Reply-To: <e72786ef-68ec-52c5-f5a8-6a5e131db2ca@smile.fr>
On Thu, Sep 01, 2022 at 12:25:03AM +0200, Romain Naour wrote:
> The gap between the kernel 6.0 and the kernel vendor (5.10) used initially is
> huge. Initially the 6.0 kernel didn't boot at all on the custom board I'm using
> with the KSZ9896. The 6.0-rc2 kernel seemed bleeding-edge enough for upstream.
If you don't plan to remain forever on a BSP based on 5.10, this is why
it is preferable to have the changes required for your platform to work
submitted upstream. It should make uprevs easier, and when there are
breakages, git bisect is at your disposal.
> > If you keep formatting development patches against the plain 6.0 release
> > candidates, you may eventually run into a conflict with some other new
> > development, and you may never even know.
>
> Actually there was no conflict until the merge of the series "net: dsa:
> microchip: add error handling and register access validation"
>
> At least I need to add the .gbit_capable entry in ksz_switch_chips[].
>
> I'm not sure about the new register validation for KSZ9896.
So there's another reason to retest on net-next.
prev parent reply other threads:[~2022-09-01 12:26 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
2022-08-31 15:51 ` Vladimir Oltean
2022-08-31 22:25 ` Romain Naour
2022-09-01 12:26 ` Vladimir Oltean [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=20220901122616.tbux3hp2oyej4wcq@skbuf \
--to=olteanv@gmail.com \
--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=pabeni@redhat.com \
--cc=romain.naour@skf.com \
--cc=romain.naour@smile.fr \
--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