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: support printk_ratelimited() in f2fs_printk()
Date: Mon, 29 Jan 2024 20:29:30 +0000 [thread overview]
Message-ID: <170656017089.16041.14974521466482956589.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240126151917.837565-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Fri, 26 Jan 2024 23:19:16 +0800 you wrote:
> This patch supports using printk_ratelimited() in f2fs_printk(), and
> wrap ratelimited f2fs_printk() into f2fs_{err,warn,info}_ratelimited(),
> then, use these new helps to clean up codes.
>
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
> fs/f2fs/compress.c | 10 +++++-----
> fs/f2fs/dir.c | 5 ++---
> fs/f2fs/f2fs.h | 40 +++++++++++++++++++++++-----------------
> fs/f2fs/super.c | 11 ++++++++---
> 4 files changed, 38 insertions(+), 28 deletions(-)
Here is the summary with links:
- [f2fs-dev,1/2] f2fs: support printk_ratelimited() in f2fs_printk()
https://git.kernel.org/jaegeuk/f2fs/c/83253fc066b9
- [f2fs-dev,2/2] f2fs: use f2fs_err_ratelimited() to avoid redundant logs
https://git.kernel.org/jaegeuk/f2fs/c/9a63d6e6382a
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:[~2024-01-29 20:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 15:19 [PATCH 1/2] f2fs: support printk_ratelimited() in f2fs_printk() Chao Yu
2024-01-26 15:19 ` [PATCH 2/2] f2fs: use f2fs_err_ratelimited() to avoid redundant logs Chao Yu
2024-01-29 20:29 ` 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=170656017089.16041.14974521466482956589.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox