From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2 1/2] f2fs: unify add/remove ino entry API for all ino types
Date: Wed, 12 Aug 2026 20:30:08 +0000 [thread overview]
Message-ID: <178656660813.2090005.5153919600313897354.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260809012639.568485-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Sun, 9 Aug 2026 09:26:38 +0800 you wrote:
> - Call f2fs_add_ino_entry() and f2fs_remove_ino_entry() for ORPHAN_INO
> - introduce __f2fs_add_ino_entry() to wrap __add_ino_entry(), so that
> both f2fs_add_ino_entry() and f2fs_set_dirty_device() will call
> __f2fs_add_ino_entry().
>
> So, after this change:
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2,1/2] f2fs: unify add/remove ino entry API for all ino types
https://git.kernel.org/jaegeuk/f2fs/c/d3915a0a356e
- [f2fs-dev,v2,2/2] f2fs: reduce memory footprint of ino management
https://git.kernel.org/jaegeuk/f2fs/c/798bddf3d9a3
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-12 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-09 1:26 [PATCH v2 1/2] f2fs: unify add/remove ino entry API for all ino types Chao Yu
2026-08-09 1:26 ` [PATCH v2 2/2] f2fs: reduce memory footprint of ino management Chao Yu
2026-08-12 20: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=178656660813.2090005.5153919600313897354.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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