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,
stable@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: fix to propagate error from f2fs_enable_checkpoint()
Date: Tue, 11 Nov 2025 22:50:14 +0000 [thread overview]
Message-ID: <176290141484.3596344.169057131556061047.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251027063534.103963-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 27 Oct 2025 14:35:33 +0800 you wrote:
> In order to let userspace detect such error rather than suffering
> silent failure.
>
> Fixes: 4354994f097d ("f2fs: checkpoint disabling")
> Cc: stable@kernel.org
> Signed-off-by: Chao Yu <chao@kernel.org>
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/2] f2fs: fix to propagate error from f2fs_enable_checkpoint()
https://git.kernel.org/jaegeuk/f2fs/c/9e2d7d763a3c
- [f2fs-dev,2/2] f2fs: block cache/dio write during f2fs_enable_checkpoint()
https://git.kernel.org/jaegeuk/f2fs/c/ba4591f78dc1
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: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, stable@kernel.org,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: fix to propagate error from f2fs_enable_checkpoint()
Date: Tue, 11 Nov 2025 22:50:14 +0000 [thread overview]
Message-ID: <176290141484.3596344.169057131556061047.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251027063534.103963-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 27 Oct 2025 14:35:33 +0800 you wrote:
> In order to let userspace detect such error rather than suffering
> silent failure.
>
> Fixes: 4354994f097d ("f2fs: checkpoint disabling")
> Cc: stable@kernel.org
> Signed-off-by: Chao Yu <chao@kernel.org>
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/2] f2fs: fix to propagate error from f2fs_enable_checkpoint()
https://git.kernel.org/jaegeuk/f2fs/c/9e2d7d763a3c
- [f2fs-dev,2/2] f2fs: block cache/dio write during f2fs_enable_checkpoint()
https://git.kernel.org/jaegeuk/f2fs/c/ba4591f78dc1
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:[~2025-11-11 22:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 6:35 [f2fs-dev] [PATCH 1/2] f2fs: fix to propagate error from f2fs_enable_checkpoint() Chao Yu via Linux-f2fs-devel
2025-10-27 6:35 ` Chao Yu
2025-10-27 6:35 ` [f2fs-dev] [PATCH 2/2] f2fs: block cache/dio write during f2fs_enable_checkpoint() Chao Yu via Linux-f2fs-devel
2025-10-27 6:35 ` Chao Yu
2025-11-11 22:50 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2025-11-11 22:50 ` [f2fs-dev] [PATCH 1/2] f2fs: fix to propagate error from f2fs_enable_checkpoint() 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=176290141484.3596344.169057131556061047.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=stable@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 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.