From: Bean Huo via Ocfs2-devel <ocfs2-devel@oss.oracle.com>
To: 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
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com,
beanhuo@micron.com
Subject: Re: [Ocfs2-devel] [PATCH v3 0/2] clean up block_commit_write
Date: Mon, 26 Jun 2023 07:58:02 +0200 [thread overview]
Message-ID: <4ced64b8089232ea94b697dec1c3595c8bf427ad.camel@iokpp.de> (raw)
In-Reply-To: <20230626054153.839672-1-beanhuo@iokpp.de>
please ignore this series patch since it has a patch-signed issue, I
have RESENT it.
On Mon, 2023-06-26 at 07:41 +0200, Bean Huo wrote:
> change log:
> v1--v2:
> 1. reordered patches
> v2-v3:
> 1. rebased patches to
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next
>
>
> Bean Huo (2):
> fs/buffer: clean up block_commit_write
> fs: convert block_commit_write to return void
>
> fs/buffer.c | 20 ++++++++------------
> fs/ext4/move_extent.c | 7 ++-----
> fs/ocfs2/file.c | 7 +------
> fs/udf/file.c | 6 +++---
> include/linux/buffer_head.h | 2 +-
> 5 files changed, 15 insertions(+), 27 deletions(-)
>
_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel
prev parent reply other threads:[~2023-06-26 5:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 5:41 [Ocfs2-devel] [PATCH v3 0/2] clean up block_commit_write Bean Huo via Ocfs2-devel
2023-06-26 5:41 ` [Ocfs2-devel] [PATCH v3 1/2] fs/buffer: " Bean Huo via Ocfs2-devel
2023-06-26 5:41 ` [Ocfs2-devel] [PATCH v3 2/2] fs: convert block_commit_write to return void Bean Huo via Ocfs2-devel
2023-06-26 5:58 ` Bean Huo via Ocfs2-devel [this message]
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=4ced64b8089232ea94b697dec1c3595c8bf427ad.camel@iokpp.de \
--to=ocfs2-devel@oss.oracle.com \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=beanhuo@iokpp.de \
--cc=beanhuo@micron.com \
--cc=brauner@kernel.org \
--cc=hch@infradead.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=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 read-only IMAP folder(s) and NNTP newsgroup(s).