From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 2/2] fsck.f2fs: fix cache offset for multiple partitions
Date: Wed, 15 Nov 2023 15:15:41 +0800 [thread overview]
Message-ID: <330cdffa-faf9-5660-4d8a-abb0ff94fbb9@kernel.org> (raw)
In-Reply-To: <20231016215849.639313-2-jaegeuk@kernel.org>
On 2023/10/17 5:58, Jaegeuk Kim wrote:
> The cache offset should have been considered multiple partitions per fd.
> Let's fix.
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2023-11-15 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 21:58 [f2fs-dev] [PATCH 1/2] Revert "f2fs-tools: do not support user-space cache" Jaegeuk Kim
2023-10-16 21:58 ` [f2fs-dev] [PATCH 2/2] fsck.f2fs: fix cache offset for multiple partitions Jaegeuk Kim
2023-11-15 7:15 ` Chao Yu [this message]
2023-11-15 7:10 ` [f2fs-dev] [PATCH 1/2] Revert "f2fs-tools: do not support user-space cache" Chao Yu
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=330cdffa-faf9-5660-4d8a-abb0ff94fbb9@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).