From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix wrong block mapping for multi-devices
Date: Fri, 10 Oct 2025 16:10:05 +0000 [thread overview]
Message-ID: <176011260525.1033062.2407373127040917969.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251007035343.806273-1-jaegeuk@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 7 Oct 2025 03:53:43 +0000 you wrote:
> Assuming the disk layout as below,
>
> disk0: 0 --- 0x00035abfff
> disk1: 0x00035ac000 --- 0x00037abfff
> disk2: 0x00037ac000 --- 0x00037ebfff
>
> and we want to read data from offset=13568 having len=128 across the block
> devices, we can illustrate the block addresses like below.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix wrong block mapping for multi-devices
https://git.kernel.org/jaegeuk/f2fs/c/7d9fdb3c9e5b
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: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, stable@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix wrong block mapping for multi-devices
Date: Fri, 10 Oct 2025 16:10:05 +0000 [thread overview]
Message-ID: <176011260525.1033062.2407373127040917969.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251007035343.806273-1-jaegeuk@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 7 Oct 2025 03:53:43 +0000 you wrote:
> Assuming the disk layout as below,
>
> disk0: 0 --- 0x00035abfff
> disk1: 0x00035ac000 --- 0x00037abfff
> disk2: 0x00037ac000 --- 0x00037ebfff
>
> and we want to read data from offset=13568 having len=128 across the block
> devices, we can illustrate the block addresses like below.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix wrong block mapping for multi-devices
https://git.kernel.org/jaegeuk/f2fs/c/7d9fdb3c9e5b
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:[~2025-10-10 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 3:53 [f2fs-dev] [PATCH] f2fs: fix wrong block mapping for multi-devices Jaegeuk Kim via Linux-f2fs-devel
2025-10-07 3:53 ` Jaegeuk Kim
2025-10-09 3:53 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-10-09 3:53 ` Chao Yu
2025-10-10 16:10 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2025-10-10 16:10 ` 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=176011260525.1033062.2407373127040917969.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=stable@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.