netdev - Re: [PATCH net-next v13 2/4] ethtool: provide customized dim profile management

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] [day] [month] [year] [list]

Message-ID: <87bbcd23-e837-477f-99b6-affe8199ce16@lunn.ch>
Date: Tue, 14 May 2024 18:36:24 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Heng Qi <hengqi@...ux.alibaba.com>
Cc: Jakub Kicinski <kuba@...nel.org>, kernel test robot <lkp@...el.com>,
	llvm@...ts.linux.dev, oe-kbuild-all@...ts.linux.dev,
	"David S . Miller" <davem@...emloft.net>,
	Paolo Abeni <pabeni@...hat.com>, Eric Dumazet <edumazet@...gle.com>,
	Jason Wang <jasowang@...hat.com>,
	"Michael S . Tsirkin" <mst@...hat.com>,
	Brett Creeley <bcreeley@....com>,
	Ratheesh Kannoth <rkannoth@...vell.com>,
	Alexander Lobakin <aleksander.lobakin@...el.com>,
	Xuan Zhuo <xuanzhuo@...ux.alibaba.com>,
	Tal Gilboa <talgi@...dia.com>, Jonathan Corbet <corbet@....net>,
	linux-doc@...r.kernel.org,
	Maxime Chevallier <maxime.chevallier@...tlin.com>,
	Jiri Pirko <jiri@...nulli.us>,
	Paul Greenwalt <paul.greenwalt@...el.com>,
	Ahmed Zaki <ahmed.zaki@...el.com>,
	Vladimir Oltean <vladimir.oltean@....com>,
	Kory Maincent <kory.maincent@...tlin.com>, justinstitt@...gle.com,
	donald.hunter@...il.com, netdev@...r.kernel.org,
	virtualization@...ts.linux.dev
Subject: Re: [PATCH net-next v13 2/4] ethtool: provide customized dim profile
 management

> One more friendly request, I see net-next is closed today, but our downstream
> kernel release deadline is 5.20, so I want to test and release the new v14 today,
> is it ok?

5.20? Didn't Linus run out of fingers and thumbs and went from 5.19 to
6.0?

Anyway, this is your internal issue, since netdev only accepts new
features patches for the next kernel release, not stable kernels. If
you are forced to do upstream first, you are going to have to wait
until the next cycle starts, and net-next reopens.

      Andrew