linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [ANNOUNCE] scsi patch queue tree
Date: Wed, 25 Jun 2014 05:41:29 -0700	[thread overview]
Message-ID: <20140625124129.GB19647@infradead.org> (raw)
In-Reply-To: <20140624155348.GA30669@infradead.org>

And here are the for-3.16 driver changes:


----------------------------------------------------------------
Brian King (2):
      ibmvscsi: Abort init sequence during error recovery
      ibmvscsi: Add memory barriers for send / receive

Maurizio Lombardi (2):
      pm8001: Fix potential null pointer dereference and memory leak.
      bnx2fc: do not scan uninitialized lists in case of error.

Neil Horman (2):
      fc: ensure scan_work isn't active when freeing fc_rport
      bnx2fc: Improve stats update mechanism

Paolo Bonzini (2):
      virtio-scsi: avoid cancelling uninitialized work items
      virtio-scsi: fix various bad behavior on aborted requests

Quinn Tran (1):
      qla2xxx: Fix sparse warning in qla_target.c.

Reddy, Sreekanth (1):
      MAINTAINERS: Update LSILOGIC MPT FUSION DRIVERS (FC/SAS/SPI) maintainers Email IDs

Tomas Henzl (2):
      be2iscsi: add an missing goto in error path
      be2iscsi: remove potential junk pointer free

 MAINTAINERS                       |    9 +++++----
 drivers/scsi/be2iscsi/be_main.c   |    2 ++
 drivers/scsi/be2iscsi/be_mgmt.c   |    4 +---
 drivers/scsi/bnx2fc/bnx2fc_fcoe.c |   16 ++++------------
 drivers/scsi/bnx2fc/bnx2fc_io.c   |    2 ++
 drivers/scsi/ibmvscsi/ibmvscsi.c  |   13 ++++++++++++-
 drivers/scsi/pm8001/pm8001_init.c |   13 ++++++++++---
 drivers/scsi/qla2xxx/qla_target.c |   17 +++++++++++------
 drivers/scsi/qla2xxx/qla_target.h |    4 ++--
 drivers/scsi/scsi_transport_fc.c  |    1 +
 drivers/scsi/virtio_scsi.c        |   26 +++++++++++++++++++++++++-
 11 files changed, 75 insertions(+), 32 deletions(-)

      reply	other threads:[~2014-06-25 12:41 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
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 [this message]

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=20140625124129.GB19647@infradead.org \
    --to=hch@infradead.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --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 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).