From: Chao Yu <chao@kernel.org>
To: Yifan Zhao <zhaoyifan@sjtu.edu.cn>, jaegeuk@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: remove redundant parameter in is_next_segment_free()
Date: Fri, 26 Apr 2024 17:41:14 +0800 [thread overview]
Message-ID: <ff6b6c5d-d325-442e-a8a3-5bb19564e92e@kernel.org> (raw)
In-Reply-To: <20240425145528.2925372-1-zhaoyifan@sjtu.edu.cn>
On 2024/4/25 22:55, Yifan Zhao wrote:
> is_next_segment_free() takes a redundant `type` parameter. Remove it.
>
> Signed-off-by: Yifan Zhao <zhaoyifan@sjtu.edu.cn>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2024-04-26 9:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 14:55 [f2fs-dev] [PATCH] f2fs: remove redundant parameter in is_next_segment_free() Yifan Zhao
2024-04-26 9:41 ` Chao Yu [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=ff6b6c5d-d325-442e-a8a3-5bb19564e92e@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zhaoyifan@sjtu.edu.cn \
/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).