public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs@kernel.org
To: Daejun Park <daejun7.park@samsung.com>
Cc: jaegeuk@kernel.org, chao@kernel.org, rostedt@goodmis.org,
	mhiramat@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	sukka.kim@samsung.com, beomsu7.kim@samsung.com
Subject: Re: [f2fs-dev] [PATCH v6] f2fs: add async reset zone command support
Date: Tue, 30 May 2023 23:40:24 +0000	[thread overview]
Message-ID: <168549002406.8773.17572147089084947715.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230508081042epcms2p8a637deae7de1829f54614e09d5fde5e5@epcms2p8>

Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Mon, 08 May 2023 17:10:42 +0900 you wrote:
> v5 -> v6
> Added trace_f2fs_iostat support for zone reset command.
> 
> v4 -> v5
> Added f2fs iostat for zone reset command.
> 
> v3 -> v4
> Fixed build error caused by unused function.
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,v6] f2fs: add async reset zone command support
    https://git.kernel.org/jaegeuk/f2fs/c/7aa6ef440cd7

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-05-30 23:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20230508081042epcms2p8a637deae7de1829f54614e09d5fde5e5@epcms2p8>
2023-05-08  8:10 ` [PATCH v6] f2fs: add async reset zone command support Daejun Park
2023-05-09 18:53   ` Jaegeuk Kim
2023-05-11  5:24     ` Daejun Park
2023-05-18  1:05       ` (2) " Jaegeuk Kim
2023-05-18  2:08         ` Daejun Park
2023-05-24  1:19           ` (2) " Jaegeuk Kim
2023-05-23 14:43     ` Steven Rostedt
2023-05-25  1:20     ` Chao Yu
2023-05-30 23:40   ` 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=168549002406.8773.17572147089084947715.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+f2fs@kernel.org \
    --cc=beomsu7.kim@samsung.com \
    --cc=chao@kernel.org \
    --cc=daejun7.park@samsung.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sukka.kim@samsung.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