From: Gao Xiang <xiang@kernel.org>
To: Nithurshen Karthikeyan <nithurshen.dev@gmail.com>
Cc: hsiangkao@linux.alibaba.com, linux-erofs@lists.ozlabs.org,
xiang@kernel.org
Subject: Re: [PATCH v2 2/2] fsck.erofs: implement concurrent directory traversal
Date: Fri, 24 Jul 2026 23:45:53 +0800 [thread overview]
Message-ID: <amOIsYxZvZpzbdVL@debian> (raw)
In-Reply-To: <CANRYsKiNaBnNrf_vG5eX9+3U+T=TRNDqDxJQh+hLPKgULZHopA@mail.gmail.com>
On Fri, Jul 24, 2026 at 09:02:38PM +0530, Nithurshen Karthikeyan wrote:
> On Fri, Jul 24, 2026 at 8:58 PM Gao Xiang <xiang@kernel.org> wrote:
> >
> > As I told you the merging policy, each patch should have no
> > regression, if concurrent directory traversal is useful, please
> > just implement it as a base, I won't accept PATCH 1/2 since
> > it has regression and useless.
> >
> As I told in the email, I am just stating that this patch is a definite
> improvement and meets the merging policy, and I will implement
> parallelised decompression on top of this patch only in a few days.
>
> I hope you could review this patch and let me know your thoughts.
So why it's called `[PATCH v2 2/2]` rather than [PATCH v6] fsck.erofs:
implement concurrent directory traversal?
>
next prev parent reply other threads:[~2026-07-24 15:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-21 12:01 [PATCH 0/2] fsck.erofs: implement multi-threaded extraction Nithurshen
2026-06-21 12:01 ` [PATCH 1/2] fsck.erofs: add multi-threaded decompression Nithurshen
2026-06-22 2:08 ` Gao Xiang
2026-06-29 9:55 ` [PATCH 1/2 v2] " Nithurshen
2026-07-05 14:00 ` Gao Xiang
2026-07-06 6:05 ` [PATCH 1/2 v3] " Nithurshen
2026-07-06 6:10 ` Nithurshen
2026-07-08 2:31 ` Gao Xiang
2026-07-13 7:02 ` [PATCH 1/2 v4] " Nithurshen
2026-06-21 12:01 ` [PATCH 2/2] fsck.erofs: implement concurrent directory traversal Nithurshen
2026-07-05 14:05 ` Gao Xiang
2026-07-14 1:10 ` [PATCH v5] fsck.erofs: add multi-threaded decompression Nithurshen
2026-07-14 1:18 ` Nithurshen Karthikeyan
2026-07-26 11:01 ` [PATCH v6] " Nithurshen
2026-07-26 11:02 ` Nithurshen
2026-07-24 14:35 ` [PATCH v2 2/2] fsck.erofs: implement concurrent directory traversal Nithurshen
2026-07-24 14:47 ` Nithurshen
2026-07-24 15:28 ` Gao Xiang
2026-07-24 15:32 ` Nithurshen Karthikeyan
2026-07-24 15:45 ` Gao Xiang [this message]
2026-07-24 15:53 ` Gao Xiang
2026-07-25 1:26 ` [PATCH v3 " Nithurshen
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=amOIsYxZvZpzbdVL@debian \
--to=xiang@kernel.org \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=nithurshen.dev@gmail.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