All of lore.kernel.org
 help / color / mirror / Atom feed
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-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: fix to convert log type to segment data type correctly
Date: Thu, 07 Nov 2024 20:30:48 +0000	[thread overview]
Message-ID: <173101144899.2084993.8424317066290373281.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241030081701.1853020-1-chao@kernel.org>

Hello:

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

On Wed, 30 Oct 2024 16:17:01 +0800 you wrote:
> This patch introduces a new helper log_type_to_seg_type() to convert
> log type to segment data type, and uses it to clean up opened codes
> in build_curseg(), and also it fixes to convert log type before use
> in do_write_page().
> 
> Signed-off-by: Chao Yu <chao@kernel.org>
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,v2] f2fs: fix to convert log type to segment data type correctly
    https://git.kernel.org/jaegeuk/f2fs/c/51d3d952c508

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 v2] f2fs: fix to convert log type to segment data type correctly
Date: Thu, 07 Nov 2024 20:30:48 +0000	[thread overview]
Message-ID: <173101144899.2084993.8424317066290373281.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241030081701.1853020-1-chao@kernel.org>

Hello:

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

On Wed, 30 Oct 2024 16:17:01 +0800 you wrote:
> This patch introduces a new helper log_type_to_seg_type() to convert
> log type to segment data type, and uses it to clean up opened codes
> in build_curseg(), and also it fixes to convert log type before use
> in do_write_page().
> 
> Signed-off-by: Chao Yu <chao@kernel.org>
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,v2] f2fs: fix to convert log type to segment data type correctly
    https://git.kernel.org/jaegeuk/f2fs/c/51d3d952c508

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



  reply	other threads:[~2024-11-07 20:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-30  8:17 [f2fs-dev] [PATCH v2] f2fs: fix to convert log type to segment data type correctly Chao Yu via Linux-f2fs-devel
2024-10-30  8:17 ` Chao Yu
2024-11-07 20:30 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2024-11-07 20:30   ` [f2fs-dev] " 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=173101144899.2084993.8424317066290373281.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 \
    /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.