linux-kernel.vger.kernel.org archive mirror
 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-kernel@vger.kernel.org,
	linux-scsi <linux-scsi@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [ANNOUNCE] scsi patch queue tree updated
Date: Fri, 15 Aug 2014 12:25:05 -0700	[thread overview]
Message-ID: <20140815192505.GA25198@infradead.org> (raw)
In-Reply-To: <1408038428.2066.42.camel@jarvis.lan>

On Thu, Aug 14, 2014 at 10:47:08AM -0700, James Bottomley wrote:
> So this is a bit late to get through linux-next and into a pull request.
> I was planning on sending the final pull tomorrow (in case Linus planned
> a surprise early release).  Can we redo some of these as bug fixes and
> send them in for -rc1?

core-for-3.17 is entirely bug fixes, the drivers side is all except
for 4 tiny patches, and even Linus isn't that anal I think.


  reply	other threads:[~2014-08-15 19:25 UTC|newest]

Thread overview: 18+ 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
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 [this message]
2014-08-15 19:32               ` James Bottomley
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=20140815192505.GA25198@infradead.org \
    --to=hch@infradead.org \
    --cc=James.Bottomley@HansenPartnership.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).