All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Hannes Reinecke <hare@suse.de>, linux-scsi@vger.kernel.org
Subject: Re: [ANNOUNCE] scsi patch queue tree
Date: Mon, 2 Jun 2014 00:58:12 -0700	[thread overview]
Message-ID: <20140602075812.GA29632@infradead.org> (raw)
In-Reply-To: <20140528105429.GA20549@infradead.org>

With Linus opening the merge window things should calm down now.

I've pushed the mvsas pciid update, and a revert of the be2scsi patch
that wasn't quite ready to the drivers-for-3.16 branch.

I've also created a new drivers-for-3.16-2 branch that contains the
remaining hpsa updates that might be too big for Linus taste that late
but should probably be fine.  I also expect to add the relatively small
lpfc update to it once I get second review in proper form.


  parent reply	other threads:[~2014-06-02  7:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-19 14:06 [ANNOUNCE] scsi patch queue tree Christoph Hellwig
2014-05-20  0:03 ` Stephen Rothwell
2014-05-20  5:39   ` Christoph Hellwig
2014-05-20 23:46     ` Stephen Rothwell
2014-05-21  2:25       ` James Bottomley
2014-05-28 10:54         ` Christoph Hellwig
2014-05-28 15:37           ` Mike Christie
2014-05-28 15:50             ` Christoph Hellwig
2014-05-28 16:04               ` Mike Christie
2014-05-28 16:05                 ` Christoph Hellwig
2014-05-28 16:01           ` Sujit Reddy Thumma
2014-05-28 16:03             ` Christoph Hellwig
2014-06-02  7:58           ` Christoph Hellwig [this message]
2014-06-02  8:25             ` Boaz Harrosh
2014-06-02  8:26               ` Christoph Hellwig
2014-06-02  8:32                 ` Boaz Harrosh
2014-06-11 12:01 ` Christoph Hellwig
2014-06-11 14:17   ` James Bottomley
2014-06-11 14:31     ` Christoph Hellwig
2014-06-24 15:52       ` Christoph Hellwig
2014-06-24 15:53         ` Christoph Hellwig
2014-06-25 12:41           ` 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=20140602075812.GA29632@infradead.org \
    --to=hch@infradead.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=hare@suse.de \
    --cc=linux-scsi@vger.kernel.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.