From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH 2/2] block: move fs/block_dev.c to block/bdev.c
Date: Tue, 7 Sep 2021 18:36:08 +0000 [thread overview]
Message-ID: <2eda6fde-af0e-fc84-6a98-6aac79457b9b@nvidia.com> (raw)
In-Reply-To: <20210907141303.1371844-3-hch@lst.de>
On 9/7/21 7:13 AM, Christoph Hellwig wrote:
> Move it together with the rest of the block layer.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
>
Looks good.
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
next prev parent reply other threads:[~2021-09-07 18:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 14:13 split and move block_dev.c Christoph Hellwig
2021-09-07 14:13 ` [PATCH 1/2] block: split out operations on block special files Christoph Hellwig
2021-09-07 18:39 ` Chaitanya Kulkarni
2021-09-07 14:13 ` [PATCH 2/2] block: move fs/block_dev.c to block/bdev.c Christoph Hellwig
2021-09-07 18:36 ` Chaitanya Kulkarni [this message]
2021-09-07 14:40 ` split and move block_dev.c 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=2eda6fde-af0e-fc84-6a98-6aac79457b9b@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.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).