From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Zhang Qilong <zhangqilong3@huawei.com>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH -next 0/3] f2fs: clean code and fix type error
Date: Tue, 13 Sep 2022 08:52:26 -0700 [thread overview]
Message-ID: <YyCnOsjAmWCsP9G9@google.com> (raw)
In-Reply-To: <20220913150604.45447-1-zhangqilong3@huawei.com>
On 09/13, Zhang Qilong wrote:
> Found serveral code type errors when review the code and fix it.
> There is no function change.
Could you please combine them into single patch?
Thanks,
>
> Zhang Qilong (3):
> f2fs: insert a space around colon
> f2fs: replace spaces with tabs
> f2fs: fix a stype error in f2fs_update_extent_tree_range
>
> fs/f2fs/data.c | 2 +-
> fs/f2fs/debug.c | 2 +-
> fs/f2fs/extent_cache.c | 2 +-
> fs/f2fs/file.c | 2 +-
> fs/f2fs/node.c | 2 +-
> 5 files changed, 5 insertions(+), 5 deletions(-)
>
> --
> 2.25.1
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2022-09-13 15:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 15:06 [f2fs-dev] [PATCH -next 0/3] f2fs: clean code and fix type error Zhang Qilong via Linux-f2fs-devel
2022-09-13 15:06 ` [f2fs-dev] [PATCH -next 1/3] f2fs: insert a space around colon Zhang Qilong via Linux-f2fs-devel
2022-09-13 15:06 ` [f2fs-dev] [PATCH -next 2/3] f2fs: replace spaces with tabs Zhang Qilong via Linux-f2fs-devel
2022-09-13 15:06 ` [f2fs-dev] [PATCH -next 3/3] f2fs: fix a stype error in f2fs_update_extent_tree_range Zhang Qilong via Linux-f2fs-devel
2022-09-13 15:52 ` Jaegeuk Kim [this message]
2022-09-14 1:08 ` [f2fs-dev] 答复: [PATCH -next 0/3] f2fs: clean code and fix type error zhangqilong via Linux-f2fs-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=YyCnOsjAmWCsP9G9@google.com \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=zhangqilong3@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.