From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>
Cc: "Roger Pau Monné" <roger.pau@citrix.com>,
"Josef Bacik" <josef@toxicpanda.com>,
"David Sterba" <dsterba@suse.com>,
"OGAWA Hirofumi" <hirofumi@mail.parknet.co.jp>,
"Konstantin Komarov" <almaz.alexandrovich@paragon-software.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"ntfs3@lists.linux.dev" <ntfs3@lists.linux.dev>
Subject: Re: [PATCH 6/7] ntfs3: use sync_blockdev_nowait
Date: Tue, 19 Oct 2021 06:34:48 +0000 [thread overview]
Message-ID: <f9c71f35-e8f1-e53d-9ace-d52e439ec505@nvidia.com> (raw)
In-Reply-To: <20211019062530.2174626-7-hch@lst.de>
On 10/18/2021 11:25 PM, Christoph Hellwig wrote:
> Use sync_blockdev_nowait instead of opencoding it.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Looks good.
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
next prev parent reply other threads:[~2021-10-19 6:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 6:25 cleanup block device inode syncing Christoph Hellwig
2021-10-19 6:25 ` [PATCH 1/7] fs: remove __sync_filesystem Christoph Hellwig
2021-10-19 6:33 ` Chaitanya Kulkarni
2021-10-19 6:25 ` [PATCH 2/7] block: remove __sync_blockdev Christoph Hellwig
2021-10-19 6:25 ` [PATCH 3/7] xen-blkback: use sync_blockdev Christoph Hellwig
2021-10-19 6:33 ` Chaitanya Kulkarni
2021-10-19 6:25 ` [PATCH 4/7] btrfs: " Christoph Hellwig
2021-10-19 6:34 ` Chaitanya Kulkarni
2021-10-19 13:54 ` David Sterba
2021-10-19 6:25 ` [PATCH 5/7] fat: use sync_blockdev_nowait Christoph Hellwig
2021-10-19 6:34 ` Chaitanya Kulkarni
2021-10-19 6:25 ` [PATCH 6/7] ntfs3: " Christoph Hellwig
2021-10-19 6:34 ` Chaitanya Kulkarni [this message]
2021-10-19 6:25 ` [PATCH 7/7] block: simplify the block device syncing code 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=f9c71f35-e8f1-e53d-9ace-d52e439ec505@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=axboe@kernel.dk \
--cc=dsterba@suse.com \
--cc=hch@lst.de \
--cc=hirofumi@mail.parknet.co.jp \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.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).