From: Greg KH <greg@kroah.com>
To: Jing Huang <huangj@Brocade.COM>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Christoph Hellwig <hch@infradead.org>,
Krishna Gudipati <kgudipat@Brocade.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
Ramkumar Vadivelu <rvadivel@Brocade.COM>,
Vinodh Ravindran <vravindr@Brocade.COM>
Subject: Re: [PATCH 2/5] bfa: Brocade BFA FC SCSI driver submission
Date: Fri, 30 Jan 2009 19:32:38 -0800 [thread overview]
Message-ID: <20090131033238.GC2947@kroah.com> (raw)
In-Reply-To: <4C94DE2070B172459E4F1EE14BD2364E02753674@HQ-EXCH-5.corp.brocade.com>
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
next prev parent reply other threads:[~2009-01-31 3:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 18:54 [PATCH 2/5] bfa: Brocade BFA FC SCSI driver submission Jing Huang
2009-01-27 22:16 ` Christoph Hellwig
2009-01-27 23:07 ` Jing Huang
2009-01-28 17:44 ` James Bottomley
2009-01-28 18:02 ` Jing Huang
2009-01-31 3:32 ` Greg KH [this message]
2009-02-01 19:03 ` Jing Huang
2009-02-04 22:46 ` Greg KH
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=20090131033238.GC2947@kroah.com \
--to=greg@kroah.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=hch@infradead.org \
--cc=huangj@Brocade.COM \
--cc=kgudipat@Brocade.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rvadivel@Brocade.COM \
--cc=vravindr@Brocade.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