From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, william.allentx@gmail.com
Subject: Re: [f2fs-dev] [PATCH 1/2] Revert: "f2fs: check in-memory block bitmap"
Date: Mon, 15 Jun 2026 15:30:06 +0000 [thread overview]
Message-ID: <178153740688.3946007.6158881733258476113.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260522065912.1756240-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Fri, 22 May 2026 14:59:11 +0800 you wrote:
> Commit 355e78913c0d ("f2fs: check in-memory block bitmap") added
> a mirror for valid block bitmap, it expects to detect in-memory
> corruption, however we never got any reports from the check points
> for almost decade, let's remove the code, it can help to save
> memories.
>
> Cc: wallentx <william.allentx@gmail.com>
> Suggested-by: Jaegeuk Kim <jaegeuk@kernel.org>
> Signed-off-by: Chao Yu <chao@kernel.org>
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/2] Revert: "f2fs: check in-memory block bitmap"
https://git.kernel.org/jaegeuk/f2fs/c/b7e85aafc96b
- [f2fs-dev,2/2] Revert: "f2fs: check in-memory sit version bitmap"
https://git.kernel.org/jaegeuk/f2fs/c/902d57fc5b84
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:[~2026-06-15 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 6:59 [f2fs-dev] [PATCH 1/2] Revert: "f2fs: check in-memory block bitmap" Chao Yu via Linux-f2fs-devel
2026-05-22 6:59 ` [f2fs-dev] [PATCH 2/2] Revert: "f2fs: check in-memory sit version bitmap" Chao Yu via Linux-f2fs-devel
2026-06-15 15:30 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [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=178153740688.3946007.6158881733258476113.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=william.allentx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox