From: patchwork-bot+f2fs@kernel.org
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: refactor f2fs_evict_inode having three major parts
Date: Tue, 11 Aug 2026 04:30:05 +0000 [thread overview]
Message-ID: <178642260514.332426.7430218840788697980.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260807220235.384637-1-jaegeuk@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Fri, 7 Aug 2026 22:02:34 +0000 you wrote:
> 1. f2fs_pre_evict_inode()
> : drop all in-memory structures
>
> 2. f2fs_delete_inode()
> : truncate inode blocks, if it was unlinked.
>
> 3. f2fs_post_evict_inode()
> : update inode records for future access
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/2] f2fs: refactor f2fs_evict_inode having three major parts
https://git.kernel.org/jaegeuk/f2fs/c/0d7477640f44
- [f2fs-dev,2/2] f2fs: call __add_ino_entry out of the eviction path
(no matching commit)
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-11 4:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 22:02 [PATCH 1/2] f2fs: refactor f2fs_evict_inode having three major parts Jaegeuk Kim
2026-08-07 22:02 ` [PATCH 2/2] f2fs: call __add_ino_entry out of the eviction path Jaegeuk Kim
2026-08-11 1:49 ` [f2fs-dev] " Chao Yu
2026-08-11 12:49 ` Chao Yu
2026-08-11 1:48 ` [f2fs-dev] [PATCH 1/2] f2fs: refactor f2fs_evict_inode having three major parts Chao Yu
2026-08-11 4: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=178642260514.332426.7430218840788697980.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 \
/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