From: Christoph Hellwig <hch@lst.de>
To: Dawei Li <set_pte_at@outlook.com>
Cc: axboe@kernel.dk, bvanassche@acm.org, hch@lst.de,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] block: simplify blksize_bits() implementation
Date: Sun, 30 Oct 2022 08:36:52 +0100 [thread overview]
Message-ID: <20221030073651.GA4131@lst.de> (raw)
In-Reply-To: <TYCP286MB23238842958D7C083D6B67CECA349@TYCP286MB2323.JPNP286.PROD.OUTLOOK.COM>
I'm not sure if it matters, but the change does look fine to me:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2022-10-30 7:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 5:20 [PATCH v3] block: simplify blksize_bits() implementation Dawei Li
2022-10-30 7:36 ` Christoph Hellwig [this message]
2022-10-30 14:34 ` Bart Van Assche
2022-10-31 2:03 ` Chaitanya Kulkarni
2022-10-31 13:27 ` 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=20221030073651.GA4131@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=set_pte_at@outlook.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.