linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Christoph Hellwig <hch@lst.de>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Dave Jiang <dave.jiang@intel.com>,
	David Milburn <dmilburn@redhat.com>,
	Ed Ciechanowski <ed.ciechanowski@intel.com>,
	Ed Nadolski <edmund.nadolski@intel.com>,
	Jacek Danecki <jacek.danecki@intel.com>,
	Jeff Skirvin <jeffrey.d.skirvin@intel.com>,
	Jeff Garzik <jeff@garzik.org>
Subject: Re: [GIT PULL] isci merge candidate
Date: Tue, 17 May 2011 15:11:24 -0700	[thread overview]
Message-ID: <BANLkTikt2JgRt0aCcN8NskNEaFXRB_pm8A@mail.gmail.com> (raw)
In-Reply-To: <1305604567.6008.5.camel@mulgrave.site>

On Mon, May 16, 2011 at 8:56 PM, James Bottomley
<James.Bottomley@hansenpartnership.com> wrote
> Give me a feel for this: If we put the driver in now, all cleanups
> effectively get postponed until .41 (because they're no longer really
> -rc candidates).  If the driver gets included in a .40-rc, we have a
> couple more months to get the basic cleanups done.

...all cleanups and the features like atapi support that were deferred
to get this initial cleanup done would be delayed until .41.

> Dan, where's the hardware release at ... as in how urgent is 39-rc last
> vs .40 rc?

Re-reviewed this internally with the latest hardware schedule and it
seems a .40-rc merge is workable.  Especially in light of the caveats
that would be specified for the .39 and .40 version of the driver if
we merged now.

>> And of course there's a lot of room for additional further cleanups
>> that should be able to shave off another couple thousands of lines, but
>> these never were on the plate for the initial merge anyway.
>
> Right ... I'm happy with the basic progress so far.

Which achieves the goal of demonstrating that the driver is on a solid
upstream trajectory.  Just need to take the opportunity to get things
finalized properly in .40-rc.

--
Dan

      reply	other threads:[~2011-05-17 22:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-13 20:14 [GIT PULL] isci merge candidate Dan Williams
2011-05-13 20:34 ` Linus Torvalds
2011-05-13 21:45   ` Dan Williams
2011-05-13 22:16     ` Benjamin Herrenschmidt
2011-05-17  0:39       ` Dan Williams
2011-05-17  0:47         ` Jeff Garzik
2011-05-17  3:41           ` Douglas Gilbert
2011-05-13 21:46   ` Jeff Garzik
2011-05-14  8:49 ` Christoph Hellwig
2011-05-17  3:56   ` James Bottomley
2011-05-17 22:11     ` Dan Williams [this message]

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=BANLkTikt2JgRt0aCcN8NskNEaFXRB_pm8A@mail.gmail.com \
    --to=dan.j.williams@intel.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=dave.jiang@intel.com \
    --cc=dmilburn@redhat.com \
    --cc=ed.ciechanowski@intel.com \
    --cc=edmund.nadolski@intel.com \
    --cc=hch@lst.de \
    --cc=jacek.danecki@intel.com \
    --cc=jeff@garzik.org \
    --cc=jeffrey.d.skirvin@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).