From: Pankaj Raghav <pankydev8@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>, Mike Snitzer <snitzer@kernel.org>,
dm-devel@redhat.com, linux-block@vger.kernel.org,
Pankaj Raghav <p.raghav@samsung.com>
Subject: Re: [PATCH 5/6] block: fold blk_max_size_offset into get_max_io_size
Date: Wed, 15 Jun 2022 12:48:21 +0200 [thread overview]
Message-ID: <20220615104821.oyuz7x3a2c4klcd5@quentin> (raw)
In-Reply-To: <20220614090934.570632-6-hch@lst.de>
On Tue, Jun 14, 2022 at 11:09:33AM +0200, Christoph Hellwig wrote:
> Now that blk_max_size_offset has a single caller left, fold it into that
> and clean up the naming convention for the local variables there.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> block/blk-merge.c | 9 +++++++--
> include/linux/blkdev.h | 19 -------------------
> 2 files changed, 7 insertions(+), 21 deletions(-)
Looks good,
Reviewed-by: Pankaj Raghav <p.raghav@samsung.com>
next prev parent reply other threads:[~2022-06-15 10:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 9:09 clean up the chunk_sizehandling helpers a little Christoph Hellwig
2022-06-14 9:09 ` [PATCH 1/6] block: factor out a chunk_size_left helper Christoph Hellwig
2022-06-14 16:39 ` Bart Van Assche
2022-06-15 10:32 ` Pankaj Raghav
2022-06-16 23:05 ` Mike Snitzer
2022-06-17 6:22 ` Christoph Hellwig
2022-06-14 9:09 ` [PATCH 2/6] dm: open code blk_max_size_offset in max_io_len Christoph Hellwig
2022-06-16 23:21 ` Mike Snitzer
2022-06-14 9:09 ` [PATCH 3/6] block: open code blk_max_size_offset in blk_rq_get_max_sectors Christoph Hellwig
2022-06-14 16:43 ` Bart Van Assche
2022-06-14 16:45 ` Bart Van Assche
2022-06-14 9:09 ` [PATCH 4/6] block: cleanup variable naming in get_max_io_size Christoph Hellwig
2022-06-14 16:50 ` Bart Van Assche
2022-06-15 6:27 ` Christoph Hellwig
2022-06-14 9:09 ` [PATCH 5/6] block: fold blk_max_size_offset into get_max_io_size Christoph Hellwig
2022-06-14 16:51 ` Bart Van Assche
2022-06-15 10:48 ` Pankaj Raghav [this message]
2022-06-14 9:09 ` [PATCH 6/6] block: move blk_queue_get_max_sectors to blk.h Christoph Hellwig
2022-06-14 16:48 ` Bart Van Assche
2022-06-17 12:39 ` clean up the chunk_sizehandling helpers a little Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2021-10-13 17:12 simplify I/O size calculation helpers v2 Christoph Hellwig
2021-10-13 17:12 ` [PATCH 5/6] block: fold blk_max_size_offset into get_max_io_size 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=20220615104821.oyuz7x3a2c4klcd5@quentin \
--to=pankydev8@gmail.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=p.raghav@samsung.com \
--cc=snitzer@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