mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Christoph Hellwig <hch@infradead.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [ANNOUNCE] scsi patch queue tree updated
Date: Mon, 4 Aug 2014 21:30:59 +1000	[thread overview]
Message-ID: <20140804213059.32fd25d5@canb.auug.org.au> (raw)
In-Reply-To: <20140804111147.GA29148@infradead.org>

[-- Attachment #1: Type: text/plain, Size: 802 bytes --]

Hi Christoph,

On Mon, 4 Aug 2014 04:11:47 -0700 Christoph Hellwig <hch@infradead.org> wrote:
>
> 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.

You realise that neither of these in linux-next as the scsi-core and
scsi-drivers trees had for-3.16 branches in the last round.  I assume I
should just drop these trees completely from linux-next?

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

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

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08 13:40 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 [this message]
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-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
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=20140804213059.32fd25d5@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=hch@infradead.org \
    --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

all inboxes | Powered by JetHome®