public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"James.Bottomley@HansenPartnership.com"
	<James.Bottomley@HansenPartnership.com>,
	"hch@lst.de" <hch@lst.de>
Subject: Re: [PATCH v2 00/12] SCSI patches for kernel v4.13
Date: Fri, 2 Jun 2017 21:10:52 +0000	[thread overview]
Message-ID: <1496437851.1214.20.camel@sandisk.com> (raw)
In-Reply-To: <yq17f0ujdxf.fsf@oracle.com>

On Fri, 2017-06-02 at 17:08 -0400, Martin K. Petersen wrote:
> > This patch series consists of the bug fixes and improvements I came up
> > with during the past two months. Please consider these patches for
> > kernel v4.13.
> 
> Does this series have dependencies on stuff that went into block for
> 4.13?

Hello Martin,

This series does not have any dependencies on pending block layer changes
and applies fine on your 4.13/queue branch. BTW, I just finished addressing
the review comments posted on v2 and am ready to post v3 of this patch series.

Bart.

      reply	other threads:[~2017-06-02 21:10 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-01 23:26 [PATCH v2 00/12] SCSI patches for kernel v4.13 Bart Van Assche
2017-06-01 23:27 ` [PATCH v2 01/12] Avoid that scsi_exit_rq() triggers a use-after-free Bart Van Assche
2017-06-02  7:16   ` Christoph Hellwig
2017-06-01 23:27 ` [PATCH v2 02/12] Split scsi_internal_device_block() Bart Van Assche
2017-06-02  7:16   ` Christoph Hellwig
2017-06-01 23:27 ` [PATCH v2 03/12] Create two versions of scsi_internal_device_unblock() Bart Van Assche
2017-06-02  7:16   ` Christoph Hellwig
2017-06-01 23:27 ` [PATCH v2 04/12] Protect SCSI device state changes with a mutex Bart Van Assche
2017-06-02  7:17   ` Christoph Hellwig
2017-06-01 23:27 ` [PATCH v2 05/12] Introduce scsi_start_queue() Bart Van Assche
2017-06-02  7:17   ` Christoph Hellwig
2017-06-01 23:27 ` [PATCH v2 06/12] Make __scsi_remove_device go straight from BLOCKED to DEL Bart Van Assche
2017-06-02  7:18   ` Christoph Hellwig
2017-06-02 20:58     ` Bart Van Assche
2017-06-01 23:27 ` [PATCH v2 07/12] Only add commands to the device command list if required by the LLD Bart Van Assche
2017-06-01 23:27 ` [PATCH v2 08/12] Introduce scsi_mq_sgl_size() Bart Van Assche
2017-06-02  7:18   ` Christoph Hellwig
2017-06-01 23:27 ` [PATCH v2 09/12] Make scsi_mq_prep_fn() call scsi_init_command() Bart Van Assche
2017-06-02  7:22   ` Christoph Hellwig
2017-06-02 17:49     ` Bart Van Assche
2017-06-01 23:27 ` [PATCH v2 10/12] snic: Remove code that zeroes driver-private command data Bart Van Assche
2017-06-02  7:22   ` Christoph Hellwig
2017-06-01 23:27 ` [PATCH v2 11/12] virtio: " Bart Van Assche
2017-06-02  7:23   ` Christoph Hellwig
2017-06-02 21:01     ` Bart Van Assche
2017-06-01 23:27 ` [PATCH v2 12/12] xen/scsifront: " Bart Van Assche
2017-06-02  7:23   ` Christoph Hellwig
2017-06-02 21:08 ` [PATCH v2 00/12] SCSI patches for kernel v4.13 Martin K. Petersen
2017-06-02 21:10   ` Bart Van Assche [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=1496437851.1214.20.camel@sandisk.com \
    --to=bart.vanassche@sandisk.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=hch@lst.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    /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