From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "hch@lst.de" <hch@lst.de>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Cc: "hare@suse.de" <hare@suse.de>
Subject: Re: [PATCH 1/2] scsi: remove various unused blist flags
Date: Wed, 21 Jun 2017 18:40:15 +0000 [thread overview]
Message-ID: <1498070412.2746.20.camel@wdc.com> (raw)
In-Reply-To: <20170619122724.32720-1-hch@lst.de>
On Mon, 2017-06-19 at 14:27 +0200, Christoph Hellwig wrote:
> [ ... ]
Reviewed-by: Bart Van Assche <bart.vanassche@wdc.com>
next prev parent reply other threads:[~2017-06-21 18:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 12:27 [PATCH 1/2] scsi: remove various unused blist flags Christoph Hellwig
2017-06-19 12:27 ` [PATCH 2/2] scsi_dh_alua: remove synchronous STPG support Christoph Hellwig
2017-06-21 18:41 ` Bart Van Assche
2017-06-26 16:43 ` Martin K. Petersen
2017-06-21 18:40 ` Bart Van Assche [this message]
2017-06-26 16:43 ` [PATCH 1/2] scsi: remove various unused blist flags Martin K. Petersen
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=1498070412.2746.20.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=hare@suse.de \
--cc=hch@lst.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 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).