From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, daehojeong@google.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/3] f2fs: fix to update upper_p in __get_secs_required() correctly
Date: Mon, 28 Jul 2025 16:50:21 +0000 [thread overview]
Message-ID: <175372142174.776676.8052673774005577055.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250724080144.3689181-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 24 Jul 2025 16:01:42 +0800 you wrote:
> Commit 1acd73edbbfe ("f2fs: fix to account dirty data in __get_secs_required()")
> missed to calculate upper_p w/ data_secs, fix it.
>
> Fixes: 1acd73edbbfe ("f2fs: fix to account dirty data in __get_secs_required()")
> Cc: Daeho Jeong <daehojeong@google.com>
> Signed-off-by: Chao Yu <chao@kernel.org>
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/3] f2fs: fix to update upper_p in __get_secs_required() correctly
https://git.kernel.org/jaegeuk/f2fs/c/6840faddb656
- [f2fs-dev,2/3] f2fs: fix to calculate dirty data during has_not_enough_free_secs()
https://git.kernel.org/jaegeuk/f2fs/c/e194e140ab7d
- [f2fs-dev,3/3] f2fs: fix to trigger foreground gc during f2fs_map_blocks() in lfs mode
https://git.kernel.org/jaegeuk/f2fs/c/1005a3ca28e9
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:[~2025-07-28 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 8:01 Chao Yu
2025-07-24 8:01 ` [PATCH 2/3] f2fs: fix to calculate dirty data during has_not_enough_free_secs() Chao Yu
2025-07-24 8:01 ` [PATCH 3/3] f2fs: fix to trigger foreground gc during f2fs_map_blocks() in lfs mode Chao Yu
2025-07-28 16:50 ` 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=175372142174.776676.8052673774005577055.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=daehojeong@google.com \
--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
all inboxes | Powered by JetHome®