From: patchwork-bot+f2fs@kernel.org
To: wangzijie <wangzijie1@honor.com>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: use f2fs_get_node_page when write inline data
Date: Mon, 05 Aug 2024 23:30:51 +0000 [thread overview]
Message-ID: <172290065197.2803.6155410196213496459.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <2073e8995f5444aeaf7133b87ec07de8@honor.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 1 Apr 2024 13:48:20 +0000 you wrote:
> From: Zijie Wang <wangzijie1@honor.com>
> Date: Mon, 1 Apr 2024 21:24:08 +0800
> Subject: [PATCH] [f2fs-dev] f2fs: use f2fs_get_node_page when write inline data
>
> We just need inode page when write inline data, use
> f2fs_get_node_page() to get it instead of using dnode_of_data,
> which can eliminate unnecessary struct use.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: use f2fs_get_node_page when write inline data
https://git.kernel.org/jaegeuk/f2fs/c/aac0828ab000
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
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+f2fs@kernel.org
To: wangzijie <wangzijie1@honor.com>
Cc: jaegeuk@kernel.org, chao@kernel.org, bintian.wang@honor.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: use f2fs_get_node_page when write inline data
Date: Mon, 05 Aug 2024 23:30:51 +0000 [thread overview]
Message-ID: <172290065197.2803.6155410196213496459.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <2073e8995f5444aeaf7133b87ec07de8@honor.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 1 Apr 2024 13:48:20 +0000 you wrote:
> From: Zijie Wang <wangzijie1@honor.com>
> Date: Mon, 1 Apr 2024 21:24:08 +0800
> Subject: [PATCH] [f2fs-dev] f2fs: use f2fs_get_node_page when write inline data
>
> We just need inode page when write inline data, use
> f2fs_get_node_page() to get it instead of using dnode_of_data,
> which can eliminate unnecessary struct use.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: use f2fs_get_node_page when write inline data
https://git.kernel.org/jaegeuk/f2fs/c/aac0828ab000
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-08-05 23:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 13:48 [f2fs-dev] [PATCH] f2fs: use f2fs_get_node_page when write inline data wangzijie
2024-04-01 13:48 ` [PATCH] [f2fs-dev] " wangzijie
2024-04-03 1:33 ` [f2fs-dev] [PATCH] " Chao Yu
2024-04-03 1:33 ` [PATCH] [f2fs-dev] " Chao Yu
2024-08-05 23:30 ` patchwork-bot+f2fs [this message]
2024-08-05 23:30 ` [f2fs-dev] [PATCH] " patchwork-bot+f2fs
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=172290065197.2803.6155410196213496459.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=wangzijie1@honor.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.