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:	Fri, 30 Jan 2009 19:32:38 -0800
From:	Greg KH <greg@...ah.com>
To:	Jing Huang <huangj@...cade.COM>
Cc:	James Bottomley <James.Bottomley@...senPartnership.com>,
	Christoph Hellwig <hch@...radead.org>,
	Krishna Gudipati <kgudipat@...cade.com>,
	linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
	Ramkumar Vadivelu <rvadivel@...cade.COM>,
	Vinodh Ravindran <vravindr@...cade.COM>
Subject: Re: [PATCH 2/5] bfa: Brocade BFA FC SCSI driver submission

On Wed, Jan 28, 2009 at 10:02:43AM -0800, Jing Huang wrote:
> > This might take a while.  I can offer to put this driver in the staging
> > tree while you work on it if that would be helpful?
> > 
> > The way the staging tree works is that drivers are held in a separate
> > area (drivers/staging) in the linux kernel while they're being worked
> > on.  The driver can be installed by users while it's in the staging tree
> > (so made use of) but it will taint the kernel with a warning that it's
> > not of linux kernel quality yet.  Once we get an acceptable driver in
> > drivers/staging, I'll move it across to drivers/scsi and remove the
> > taint.
> > 
> > James
> > 
> > 
> 
> This is definitely helpful, thanks James!

Does this mean someone will send me a patch to add this to the
drivers/staging/ tree?  Or should I just grab these patches and use them
to add them to the tree myself (preserving author attributes of course)?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ