From: patchwork-bot+f2fs@kernel.org
To: Julian Sun <sunjunchao2870@gmail.com>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2 1/2] f2fs: fix macro definition on_f2fs_build_free_nids
Date: Mon, 05 Aug 2024 23:30:51 +0000 [thread overview]
Message-ID: <172290065178.2803.508763440418815514.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240722023913.54788-1-sunjunchao2870@gmail.com>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Sun, 21 Jul 2024 22:39:12 -0400 you wrote:
> The macro on_f2fs_build_free_nids accepts a parameter nmi,
> but it was not used, rather the variable nm_i was directly used,
> which may be a local variable inside a function that calls the macros.
>
> Signed-off-by: Julian Sun <sunjunchao2870@gmail.com>
> ---
> fs/f2fs/node.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Here is the summary with links:
- [f2fs-dev,v2,1/2] f2fs: fix macro definition on_f2fs_build_free_nids
https://git.kernel.org/jaegeuk/f2fs/c/d1e1ff971d1a
- [f2fs-dev,v2,2/2] f2fs: fix macro definition stat_inc_cp_count
https://git.kernel.org/jaegeuk/f2fs/c/d72750e4a752
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
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-08-05 23:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 2:39 [f2fs-dev] [PATCH v2 1/2] f2fs: fix macro definition on_f2fs_build_free_nids Julian Sun
2024-07-22 2:39 ` [f2fs-dev] [PATCH v2 2/2] f2fs: fix macro definition stat_inc_cp_count Julian Sun
2024-07-26 1:11 ` Chao Yu
2024-07-26 1:11 ` [f2fs-dev] [PATCH v2 1/2] f2fs: fix macro definition on_f2fs_build_free_nids Chao Yu
2024-08-05 23:30 ` patchwork-bot+f2fs [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=172290065178.2803.508763440418815514.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=sunjunchao2870@gmail.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.