From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>
Cc: Justin Sanders <justin@coraid.com>,
Josef Bacik <josef@toxicpanda.com>,
Xianting Tian <xianting_tian@126.com>,
linux-block@vger.kernel.org, dm-devel@redhat.com,
Stefan Haberland <sth@linux.ibm.com>,
Jan Hoeppner <hoeppner@linux.ibm.com>,
linux-kernel@vger.kernel.org, nbd@other.debian.org,
linux-nvme@lists.infradead.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH 1/2] block: replace bd_set_size with bd_set_nr_sectors
Date: Fri, 21 Aug 2020 11:24:17 +0200 [thread overview]
Message-ID: <93b6d1f0-84e5-d1b9-ac00-bfb61968e2aa@suse.de> (raw)
In-Reply-To: <20200821085600.2395666-2-hch@lst.de>
On 8/21/20 10:55 AM, Christoph Hellwig wrote:
> Replace bd_set_size with a version that takes the number of sectors
> instead, as that fits most of the current and future callers much better.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> drivers/block/loop.c | 4 ++--
> drivers/block/nbd.c | 7 ++++---
> drivers/block/pktcdvd.c | 2 +-
> drivers/nvme/host/nvme.h | 2 +-
> fs/block_dev.c | 10 +++++-----
> include/linux/genhd.h | 2 +-
> 6 files changed, 14 insertions(+), 13 deletions(-)
>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), GF: Felix Imendörffer
next prev parent reply other threads:[~2020-08-21 9:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 8:55 fix block device size update serialization Christoph Hellwig
2020-08-21 8:55 ` [PATCH 1/2] block: replace bd_set_size with bd_set_nr_sectors Christoph Hellwig
2020-08-21 9:24 ` Hannes Reinecke [this message]
2020-08-21 8:56 ` [PATCH 2/2] block: fix locking for struct block_device size updates Christoph Hellwig
2020-08-21 9:26 ` Hannes Reinecke
[not found] ` <133efc8b.1649.17410784734.Coremail.xianting_tian@126.com>
2020-08-23 9:09 ` Christoph Hellwig
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=93b6d1f0-84e5-d1b9-ac00-bfb61968e2aa@suse.de \
--to=hare@suse.de \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=hoeppner@linux.ibm.com \
--cc=josef@toxicpanda.com \
--cc=justin@coraid.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=nbd@other.debian.org \
--cc=sth@linux.ibm.com \
--cc=xianting_tian@126.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
all inboxes | Powered by JetHome®