From: Christoph Hellwig <hch@infradead.org>
To: Bean Huo <beanhuo@iokpp.de>
Cc: viro@zeniv.linux.org.uk, brauner@kernel.org,
akpm@linux-foundation.org, jack@suse.cz, jack@suse.com,
tytso@mit.edu, adilger.kernel@dilger.ca, mark@fasheh.com,
jlbec@evilplan.org, joseph.qi@linux.alibaba.com,
willy@infradead.org, hch@infradead.org,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com,
beanhuo@micron.com
Subject: Re: [RESEND PATCH v3 1/2] fs/buffer: clean up block_commit_write
Date: Mon, 26 Jun 2023 00:55:31 -0700 [thread overview]
Message-ID: <ZJlEc1+jRaV0REOL@infradead.org> (raw)
In-Reply-To: <20230626055518.842392-2-beanhuo@iokpp.de>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2023-06-26 7:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 5:55 [RESEND PATCH v3 0/2] clean up block_commit_write Bean Huo
2023-06-26 5:55 ` [RESEND PATCH v3 1/2] fs/buffer: " Bean Huo
2023-06-26 7:55 ` Christoph Hellwig [this message]
2023-06-26 12:21 ` Matthew Wilcox
2023-06-26 13:41 ` Jan Kara
2023-06-26 5:55 ` [RESEND PATCH v3 2/2] fs: convert block_commit_write to return void Bean Huo
2023-06-26 7:55 ` Christoph Hellwig
2023-06-26 12:21 ` Matthew Wilcox
2023-06-26 12:26 ` [RESEND PATCH v3 0/2] clean up block_commit_write Matthew Wilcox
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=ZJlEc1+jRaV0REOL@infradead.org \
--to=hch@infradead.org \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=beanhuo@iokpp.de \
--cc=beanhuo@micron.com \
--cc=brauner@kernel.org \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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).