All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Dan Williams <dan.j.williams@intel.com>,
	james.bottomley@suse.de, dave.jiang@intel.com,
	linux-scsi@vger.kernel.org, jacek.danecki@intel.com,
	ed.ciechanowski@intel.com, jeffrey.d.skirvin@intel.com,
	edmund.nadolski@intel.com
Subject: Re: [RFC PATCH 00/10] isci: core
Date: Tue, 15 Mar 2011 14:08:58 -0400	[thread overview]
Message-ID: <4D7FAB3A.9060903@garzik.org> (raw)
In-Reply-To: <20110315175533.GA8291@infradead.org>

On 03/15/2011 01:55 PM, Christoph Hellwig wrote:
> On Tue, Mar 15, 2011 at 01:47:12PM -0400, Jeff Garzik wrote:
>> Let's get this driver into staging for 2.6.39, if it isn't going to
>> hit the merge window for 2.6.39.
>>
>> It would lame for such [presumably] high volume hardware to be in
>> neither the main kernel, nor staging, at 2.6.39 release time.
>
> What's the point of staging?  That just causes tons of poinless churn.
> Linus has made it clear that normal high volume hardware drivers can go
> in after the merge window.  So let's just polish it for another few
> weeks and then put it in where it belongs.

That's fine... if that really happens.

It seemed like this was turning into another driver that would get held 
outside the kernel until it's "perfect."  If that is the case, Linus has 
also made it clear we should get drivers for high volume, shipping 
hardware into the kernel, even if its staging, if the alternative is to 
deny users the driver.

	Jeff




  reply	other threads:[~2011-03-15 18:09 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-10 10:54 [RFC PATCH 00/10] isci: core Dan Williams
2011-03-10 10:54 ` [RFC PATCH 01/10] isci/core: controller Dan Williams
2011-03-10 10:54 ` [RFC PATCH 02/10] isci/core: phy Dan Williams
2011-03-10 10:54 ` [RFC PATCH 03/10] isci/core: port Dan Williams
2011-03-10 10:54 ` [RFC PATCH 04/10] isci/core: remote device Dan Williams
2011-03-10 10:54 ` [RFC PATCH 05/10] isci/core: remote node context Dan Williams
2011-03-10 10:54 ` [RFC PATCH 06/10] isci/core: stp Dan Williams
2011-03-10 10:54 ` [RFC PATCH 07/10] isci/core: request (general, ssp and smp) Dan Williams
2011-03-10 10:55 ` [RFC PATCH 08/10] isci/core: unsolicited frame handling and registers Dan Williams
2011-03-10 10:55 ` [RFC PATCH 09/10] isci/core: base state machine and memory descriptors Dan Williams
2011-03-10 10:55 ` [RFC PATCH 10/10] isci/core: common definitions and utility functions Dan Williams
2011-03-30 14:37   ` Christoph Hellwig
2011-03-15 17:47 ` [RFC PATCH 00/10] isci: core Jeff Garzik
2011-03-15 17:55   ` Christoph Hellwig
2011-03-15 18:08     ` Jeff Garzik [this message]
2011-03-15 20:13       ` Dan Williams
2011-03-15 21:04         ` Jeff Garzik
2011-03-18 15:56 ` Christoph Hellwig
2011-03-19  6:19   ` Dan Williams
2011-03-27 22:32 ` Christoph Hellwig
2011-03-30  1:22   ` Dan Williams
2011-03-30  7:23     ` Christoph Hellwig
2011-03-31  0:20       ` Dan Williams
2011-03-31  6:32         ` Christoph Hellwig

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=4D7FAB3A.9060903@garzik.org \
    --to=jeff@garzik.org \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=ed.ciechanowski@intel.com \
    --cc=edmund.nadolski@intel.com \
    --cc=hch@infradead.org \
    --cc=jacek.danecki@intel.com \
    --cc=james.bottomley@suse.de \
    --cc=jeffrey.d.skirvin@intel.com \
    --cc=linux-scsi@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.