From: Christoph Hellwig <hch@infradead.org>
To: Bart Van Assche <bart.vanassche@wdc.com>
Cc: "Jens Axboe" <axboe@kernel.dk>,
linux-block@vger.kernel.org, "Christoph Hellwig" <hch@lst.de>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
xen-devel@lists.xenproject.org, stable@vger.kernel.org
Subject: Re: [PATCH] xen-blkfront: Fix handling of non-supported operations
Date: Mon, 24 Jul 2017 01:02:03 -0700 [thread overview]
Message-ID: <20170724080203.GA16484@infradead.org> (raw)
In-Reply-To: <20170721171110.824-1-bart.vanassche@wdc.com>
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2017-07-24 8:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 17:11 [PATCH] xen-blkfront: Fix handling of non-supported operations Bart Van Assche
2017-07-24 8:02 ` Christoph Hellwig [this message]
2017-07-24 14:46 ` Jens Axboe
2017-07-24 15:10 ` Bart Van Assche
2017-07-24 21:20 ` Omar Sandoval
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=20170724080203.GA16484@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=bart.vanassche@wdc.com \
--cc=hch@lst.de \
--cc=konrad.wilk@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=roger.pau@citrix.com \
--cc=stable@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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).