All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [ANNOUNCE] scsi patch queue tree updated
Date: Mon, 4 Aug 2014 04:11:47 -0700	[thread overview]
Message-ID: <20140804111147.GA29148@infradead.org> (raw)
In-Reply-To: <1406925121.2654.21.camel@jarvis>

On Fri, Aug 01, 2014 at 04:32:01PM -0400, James Bottomley wrote:
> On Fri, 2014-08-01 at 05:20 -0700, Christoph Hellwig wrote:
> > I've pushed out updates to both the core-for-3.17 and drivers-for-3.17
> > branches.
> 
> So I'm afraid we missed the last -next build on these, so they can't go
> in with the early SCSI pull.  I'm open to doing one mid merge window,
> but Linus tends not to like that.

I don't think there are any hard and fast rules.


The core-for-3.17 commit is a trivial printk specifier regression fix for
something introduced in the 3.17 merge window, so pulling it in is
an absolute non-brainer.

The drivers side are a bunch of smaller fixes for iscsi and pm8001 which
never have been a problem to put in near the end of the merge window,
especially if they have a few more days linux-next exposure in
Linux-next even after the 3.16 release.  They absolutely would be
candidates for a second pull even if they'd miss the first pull.

  reply	other threads:[~2014-08-04 11:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08 13:40 [ANNOUNCE] scsi patch queue tree updated Christoph Hellwig
2014-08-01 12:20 ` Christoph Hellwig
2014-08-01 20:32   ` James Bottomley
2014-08-04 11:11     ` Christoph Hellwig [this message]
2014-08-04 11:30       ` Stephen Rothwell
2014-08-04 11:34         ` Christoph Hellwig
2014-08-04 11:39           ` Stephen Rothwell
2014-08-04 14:20       ` James Bottomley
2014-08-14 12:54         ` Christoph Hellwig
2014-08-14 17:47           ` James Bottomley
2014-08-15 19:25             ` Christoph Hellwig
2014-08-15 19:32               ` James Bottomley
2014-08-21 19:33   ` adam radford
2014-08-21 19:50     ` Christoph Hellwig
2014-08-21 20:00       ` Martin K. Petersen
2014-08-21 20:26       ` Martin K. Petersen
2014-08-21 21:58         ` Christoph Hellwig
2014-09-15 22:58   ` Christoph Hellwig
2014-09-16 21:37     ` Christoph Hellwig
2014-09-16 21:44       ` James Bottomley
2014-12-30 13:02 ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2014-07-18 10:02 Christoph Hellwig
2014-07-25 21:19 ` 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=20140804111147.GA29148@infradead.org \
    --to=hch@infradead.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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 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.