From: Bean Huo via Ocfs2-devel <ocfs2-devel@oss.oracle.com>
To: Jan Kara <jack@suse.cz>, Bean Huo <beanhuo@iokpp.de>
Cc: brauner@kernel.org, tytso@mit.edu, linux-kernel@vger.kernel.org,
beanhuo@micron.com, adilger.kernel@dilger.ca,
viro@zeniv.linux.org.uk, jack@suse.com,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
ocfs2-devel@oss.oracle.com
Subject: Re: [Ocfs2-devel] [PATCH v1 2/5] fs/buffer.c: convert block_commit_write to return void
Date: Mon, 19 Jun 2023 12:42:02 +0200 [thread overview]
Message-ID: <efb4cbf2ee6f006b2b458c209fc0f31e8ba655e2.camel@gmail.com> (raw)
In-Reply-To: <20230619095604.uknf7uovnn2az2wu@quack3>
On Mon, 2023-06-19 at 11:56 +0200, Jan Kara wrote:
> Looks good to me but you'll need to reorder this patch at the end of
> the
> patch series to avoid breaking compilation in the middle of the
> series.
> Otherwise feel free to add:
>
> Reviewed-by: Jan Kara <jack@suse.cz>
>
> Honza
thanks Jan, I will reorder it in the v2.
Kind regards,
Bean
_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel
next prev parent reply other threads:[~2023-06-20 14:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 21:32 [Ocfs2-devel] [PATCH v1 0/5] clean up block_commit_write Bean Huo via Ocfs2-devel
2023-06-18 21:32 ` [Ocfs2-devel] [PATCH v1 1/5] fs/buffer: " Bean Huo via Ocfs2-devel
2023-06-19 9:52 ` Jan Kara via Ocfs2-devel
2023-06-18 21:32 ` [Ocfs2-devel] [PATCH v1 2/5] fs/buffer.c: convert block_commit_write to return void Bean Huo via Ocfs2-devel
2023-06-18 23:35 ` kernel test robot via Ocfs2-devel
2023-06-19 9:56 ` Jan Kara via Ocfs2-devel
2023-06-19 10:42 ` Bean Huo via Ocfs2-devel [this message]
2023-06-18 21:32 ` [Ocfs2-devel] [PATCH v1 3/5] ext4: No need to check return value of block_commit_write() Bean Huo via Ocfs2-devel
2023-06-19 9:56 ` Jan Kara via Ocfs2-devel
2023-06-18 21:32 ` [Ocfs2-devel] [PATCH v1 4/5] fs/ocfs2: " Bean Huo via Ocfs2-devel
2023-06-19 9:56 ` Jan Kara via Ocfs2-devel
2023-06-18 21:32 ` [Ocfs2-devel] [PATCH v1 5/5] udf: " Bean Huo via Ocfs2-devel
2023-06-19 9:56 ` Jan Kara via Ocfs2-devel
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=efb4cbf2ee6f006b2b458c209fc0f31e8ba655e2.camel@gmail.com \
--to=ocfs2-devel@oss.oracle.com \
--cc=adilger.kernel@dilger.ca \
--cc=beanhuo@iokpp.de \
--cc=beanhuo@micron.com \
--cc=brauner@kernel.org \
--cc=huobean@gmail.com \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).