From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-efi@vger.kernel.org, linux-s390@vger.kernel.org,
Jan Hoeppner <hoeppner@linux.ibm.com>,
Stefan Haberland <sth@linux.ibm.com>,
Davidlohr Bueso <dave@stgolabs.net>,
linux-block@vger.kernel.org
Subject: Re: more bdev_nr_sectors / bdev_nr_bytes conversions
Date: Tue, 19 Oct 2021 06:18:05 -0600 [thread overview]
Message-ID: <163464587890.599826.15140587721963730407.b4-ty@kernel.dk> (raw)
In-Reply-To: <20211019062024.2171074-1-hch@lst.de>
On Tue, 19 Oct 2021 08:20:21 +0200, Christoph Hellwig wrote:
> these somehow slipped into a different branch, so here is another
> small batch.
>
> Diffstat:
> ioctl.c | 20 ++++++++------------
> partitions/efi.c | 2 +-
> partitions/ibm.c | 19 ++++++++++---------
> 3 files changed, 19 insertions(+), 22 deletions(-)
>
> [...]
Applied, thanks!
[1/3] block/ioctl: use bdev_nr_sectors and bdev_nr_bytes
commit: 946e99373037be4841e8b42dcd136e03093c9fd5
[2/3] partitions/efi: use bdev_nr_bytes instead of open coding it
commit: f9831b885709978ed9d16833ceeb3a2ec174a2d2
[3/3] partitions/ibm: use bdev_nr_sectors instead of open coding it
commit: 97eeb5fc14cc4b2091df8b841a07a1ac69f2d762
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2021-10-19 12:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 6:20 more bdev_nr_sectors / bdev_nr_bytes conversions Christoph Hellwig
2021-10-19 6:20 ` [PATCH 1/3] block/ioctl: use bdev_nr_sectors and bdev_nr_bytes Christoph Hellwig
2021-10-19 6:20 ` [PATCH 2/3] partitions/efi: use bdev_nr_bytes instead of open coding it Christoph Hellwig
2021-10-19 6:20 ` [PATCH 3/3] partitions/ibm: use bdev_nr_sectors " Christoph Hellwig
2021-10-19 7:01 ` Ard Biesheuvel
2021-10-19 12:18 ` Jens Axboe [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=163464587890.599826.15140587721963730407.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=dave@stgolabs.net \
--cc=hch@lst.de \
--cc=hoeppner@linux.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=sth@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).