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 1/2] f2fs: remove unused GC_FAILURE_PIN
Date: Sat, 11 May 2024 00:50:33 +0000 [thread overview]
Message-ID: <171538863379.11229.10303320996620120996.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240506104538.778116-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 6 May 2024 18:45:37 +0800 you wrote:
> After commit 3db1de0e582c ("f2fs: change the current atomic write way"),
> we removed all GC_FAILURE_ATOMIC usage, let's change i_gc_failures[]
> array to i_pin_failure for cleanup.
>
> Meanwhile, let's define i_current_depth and i_gc_failures as union
> variable due to they won't be valid at the same time.
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/2] f2fs: remove unused GC_FAILURE_PIN
https://git.kernel.org/jaegeuk/f2fs/c/968c4f72b23c
- [f2fs-dev,2/2] f2fs: fix to limit gc_pin_file_threshold
https://git.kernel.org/jaegeuk/f2fs/c/c521a6ab4ad7
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, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: remove unused GC_FAILURE_PIN
Date: Sat, 11 May 2024 00:50:33 +0000 [thread overview]
Message-ID: <171538863379.11229.10303320996620120996.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240506104538.778116-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 6 May 2024 18:45:37 +0800 you wrote:
> After commit 3db1de0e582c ("f2fs: change the current atomic write way"),
> we removed all GC_FAILURE_ATOMIC usage, let's change i_gc_failures[]
> array to i_pin_failure for cleanup.
>
> Meanwhile, let's define i_current_depth and i_gc_failures as union
> variable due to they won't be valid at the same time.
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/2] f2fs: remove unused GC_FAILURE_PIN
https://git.kernel.org/jaegeuk/f2fs/c/968c4f72b23c
- [f2fs-dev,2/2] f2fs: fix to limit gc_pin_file_threshold
https://git.kernel.org/jaegeuk/f2fs/c/c521a6ab4ad7
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:[~2024-05-11 0:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 10:45 [f2fs-dev] [PATCH 1/2] f2fs: remove unused GC_FAILURE_PIN Chao Yu
2024-05-06 10:45 ` Chao Yu
2024-05-06 10:45 ` [f2fs-dev] [PATCH 2/2] f2fs: fix to limit gc_pin_file_threshold Chao Yu
2024-05-06 10:45 ` Chao Yu
2024-05-11 0:50 ` patchwork-bot+f2fs [this message]
2024-05-11 0:50 ` [f2fs-dev] [PATCH 1/2] f2fs: remove unused GC_FAILURE_PIN 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=171538863379.11229.10303320996620120996.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 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.