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: Wed, 31 Aug 2022 18:51:03 +0300 [thread overview]
Message-ID: <20220831155103.2v7lfzierdji3p3e@skbuf> (raw)
In-Reply-To: <e7ba61d7-de75-3cfe-ee92-3f234dd36289@smile.fr>
On Wed, Aug 31, 2022 at 05:43:27PM +0200, Romain Naour wrote:
> 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?
The kernel development process is that you normally test a patch on the
git tree on which it is to be eventually applied.
The net-next.git tree is periodically (weekly) merged with the 6.0
release candidates where bug fixes land, but it contains newly developed
material intended for the 6.1 release candidates (hence the "next" name).
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.
next prev parent reply other threads:[~2022-08-31 15:51 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 [this message]
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=20220831155103.2v7lfzierdji3p3e@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