lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220831155103.2v7lfzierdji3p3e@skbuf>
Date:   Wed, 31 Aug 2022 18:51:03 +0300
From:   Vladimir Oltean <olteanv@...il.com>
To:     Romain Naour <romain.naour@...le.fr>
Cc:     netdev@...r.kernel.org, linux@...linux.org.uk, pabeni@...hat.com,
        kuba@...nel.org, edumazet@...gle.com, davem@...emloft.net,
        f.fainelli@...il.com, vivien.didelot@...il.com, andrew@...n.ch,
        UNGLinuxDriver@...rochip.com, woojung.huh@...rochip.com,
        Romain Naour <romain.naour@....com>,
        Arun Ramadoss <arun.ramadoss@...rochip.com>
Subject: Re: [PATCH v2 1/2] net: dsa: microchip: add KSZ9896 switch support

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.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ