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]
Date: Wed, 21 Jun 2023 21:44:55 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Jakub Kicinski <kuba@...nel.org>
Cc: "Linga, Pavan Kumar" <pavan.kumar.linga@...el.com>,
	Tony Nguyen <anthony.l.nguyen@...el.com>, davem@...emloft.net,
	pabeni@...hat.com, edumazet@...gle.com, netdev@...r.kernel.org,
	emil.s.tantilov@...el.com, jesse.brandeburg@...el.com,
	sridhar.samudrala@...el.com, shiraz.saleem@...el.com,
	sindhu.devale@...el.com, willemb@...gle.com, decot@...gle.com,
	leon@...nel.org, mst@...hat.com, simon.horman@...igine.com,
	shannon.nelson@....com, stephen@...workplumber.org
Subject: Re: [PATCH net-next v3 00/15][pull request] Introduce Intel IDPF
 driver

On Wed, Jun 21, 2023 at 12:28:53PM -0700, Jakub Kicinski wrote:
> On Wed, 21 Jun 2023 12:13:06 -0700 Linga, Pavan Kumar wrote:
> > Thanks for the feedback. Given the timing and type of changes requested 
> > for the patches, would it be possible to accept this patch series (v3) 
> > in its current form, as we continue to develop and address all the 
> > feedback in followup patches?
> 
> I think you're asking to be accepted in a Linux-Staging kind of a way?

Or maybe real staging, driver/staging ? Add a TODO and GregKH might
accept it.

    2.5. Staging trees

    The kernel source tree contains the drivers/staging/ directory,
    where many sub-directories for drivers or filesystems that are on
    their way to being added to the kernel tree live. They remain in
    drivers/staging while they still need more work; once complete,
    they can be moved into the kernel proper. This is a way to keep
    track of drivers that aren't up to Linux kernel coding or quality
    standards, but people may want to use them and track development.

Andrew

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ