From: Sagi Grimberg <sagi@grimberg.me>
To: Ilya Dryomov <idryomov@gmail.com>, linux-block@vger.kernel.org
Cc: Jens Axboe <axboe@fb.com>, Christoph Hellwig <hch@infradead.org>,
Tejun Heo <tj@kernel.org>, David Disseldorp <ddiss@suse.de>
Subject: Re: [PATCH v3 2/2] block: add bdev_read_only() checks to common helpers
Date: Sun, 14 Jan 2018 11:35:12 +0200 [thread overview]
Message-ID: <5a6fe1df-df7a-b8e7-697b-3f098b1fd4e4@grimberg.me> (raw)
In-Reply-To: <1515676152-18476-3-git-send-email-idryomov@gmail.com>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
next prev parent reply other threads:[~2018-01-14 9:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 13:09 [PATCH v3 0/2] block: enforce ioctl(BLKROSET) and set_disk_ro() Ilya Dryomov
2018-01-11 13:09 ` [PATCH v3 1/2] block: fail op_is_write() requests to read-only partitions Ilya Dryomov
2018-01-14 9:35 ` Sagi Grimberg
2018-01-11 13:09 ` [PATCH v3 2/2] block: add bdev_read_only() checks to common helpers Ilya Dryomov
2018-01-14 9:35 ` Sagi Grimberg [this message]
2018-01-18 11:16 ` [PATCH v3 0/2] block: enforce ioctl(BLKROSET) and set_disk_ro() Ilya Dryomov
2018-01-18 19:57 ` Jens Axboe
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=5a6fe1df-df7a-b8e7-697b-3f098b1fd4e4@grimberg.me \
--to=sagi@grimberg.me \
--cc=axboe@fb.com \
--cc=ddiss@suse.de \
--cc=hch@infradead.org \
--cc=idryomov@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=tj@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).