Re: [GIT PULL] async scsi resume for 3.15

2014-04-11 Thread James Bottomley 
On Thu, 2014-04-10 at 18:24 -0700, Dan Williams wrote:
 Hi Linus,
 
 James might still be in the process of sending this your way.  However,
 given the proximity to -rc1, my reasoning for sending this directly is:
 
 1/ It provides a tangible speed up for a non-esoteric use case (laptop
 resume):
 
   
 https://01.org/suspendresume/blogs/tebrandt/2013/hard-disk-resume-optimization-simpler-approach
 
 2/ You already pulled the first half of this enabling from Tejun.
 Quoting Tejun's ATA pull request:
 
   Dan finishes the patchset to make libata PM operations
asynchronous.  Combined with one patch being routed through scsi,
this should speed resume measurably.
 
 3/ As far as I can tell it is acceptable to James:
 
   http://marc.info/?l=linux-scsim=139499409510791w=2
   http://marc.info/?l=linux-scsim=139508044602605w=2
   http://marc.info/?l=linux-scsim=139536062515216w=2
 
 4/ I promised Todd I would get it upstream before he returns from
 vacation.
 
 Please pull, thank you.

OK, so this missed the SCSI cutoff window because the series wasn't
finalised until 17 March and, originally, I thought Linus would cut us
off at -rc7 which was 16 March.  In reality we got an extra week, but I
spent that ironing out a few late arriving bugs in the tree itself
rather than integrating features.

For drivers, I'm willing to buck the release protocols a bit because
they're self contained, but for core features, they are supposed to be
all finalised by -rc5.  Plus Linus bites me every time I do it even for
drivers, so I was actually letting the scars heal a bit.

I also don't see this in linux-next, unless I'm not looking in the right
place, so it would be a bit of a risk adding it just before -rc1.

James


--
To unsubscribe from this list: send the line unsubscribe linux-scsi in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [GIT PULL] async scsi resume for 3.15

2014-04-11 Thread Linus Torvalds 
On Fri, Apr 11, 2014 at 11:20 AM, James Bottomley
james.bottom...@hansenpartnership.com wrote:

 I also don't see this in linux-next, unless I'm not looking in the right
 place, so it would be a bit of a risk adding it just before -rc1.

.. but it sounds like you're not against it? I'll pull it - in the
chaos that is 3.15-rc1, this is the least of my worries. This has been
the biggest (by far) merge window so far, afaik. Might as well take
this too.

  Linus
--
To unsubscribe from this list: send the line unsubscribe linux-scsi in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [GIT PULL] async scsi resume for 3.15

2014-04-11 Thread Linus Torvalds 
On Fri, Apr 11, 2014 at 5:23 PM, Linus Torvalds
torva...@linux-foundation.org wrote:

 This has been the biggest (by far) merge window so far, afaik.
 Might as well take this too.

Actually, I take that by far back. In fact it's not even the biggest
one (yet). It looks like 3.10-rc1 was worse in number of commits, and
v3.7-rc1 was bigger in number of lines and files.

That may still change by the time I tag rc1, but it looks like while
the current merge window is big, it's not actually going to break any
records.

Regardless, I pulled the async scsi resume patch.

  Linus
--
To unsubscribe from this list: send the line unsubscribe linux-scsi in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html