From: Zorro Lang <zlang@kernel.org>
To: Prabhakar Pujeri <prabhakar.pujeri@dell.com>
Cc: fstests@vger.kernel.org, "Darrick J. Wong" <djwong@kernel.org>
Subject: Re: [PATCH v2 0/3] xfstests: add missing _require_scratch checks
Date: Thu, 3 Sep 2026 21:53:39 +0800 [thread overview]
Message-ID: <apl53bE5aZMJmZII@zlang-mailbox> (raw)
In-Reply-To: <20260903035344.752-1-prabhakar.pujeri@dell.com>
On Thu, Sep 03, 2026 at 03:53:41AM +0000, Prabhakar Pujeri wrote:
> Consolidated resend of the remaining _require_scratch fixes, as
> requested by Zorro. The first three of this batch (btrfs/333 v3,
> overlay/081 v2, btrfs/273 v2) are already in his local tree.
>
> v2:
> - Resent as a single series, per Zorro's request.
> - Carry Darrick J. Wong's Reviewed-by (generic/590,735 and generic/795)
> and Zorro Lang's Reviewed-by (f2fs/015,016); besides message
> re-formatting there is no code change.
>
> v1 pieces for reference:
> - generic/590,735: https://lore.kernel.org/fstests/20260831104148.2243-1-prabhakar.pujeri@dell.com/
> - generic/795: https://lore.kernel.org/fstests/20260902050139.2426-1-prabhakar.pujeri@dell.com/
> - f2fs/015,016: https://lore.kernel.org/fstests/20260902050133.2413-1-prabhakar.pujeri@dell.com/
>
>
> Prabhakar Pujeri (3):
> generic/590,735: add missing _require_scratch check
> generic/795: add missing _require_scratch check
> f2fs/015,016: add missing _require_scratch checks
Hi,
Thanks for this work, I'm wondering why generic/590 and generic/735 are
combined into one patch while generic/795 is split out?
Given that they all just add a single line of _require_scratch. While I think
this could easily be a single patch, if you prefer splitting them up, grouping
them per-directory (generic, f2fs, btrfs, overlay ...) would make sense.
Also, I recall you had a few other similar patches, such as:
btrfs/333: require scratch before checking encoded reads
btrfs/273: add missing _require_scratch check
overlay/081: add missing _require_scratch check
Please bundle all of them into a single patch series (keeping any existing
Reviewed-by tags) so they can be reviewed and merged together.
Thanks,
Zorro
>
> tests/f2fs/015 | 1 +
> tests/f2fs/016 | 1 +
> tests/generic/590 | 1 +
> tests/generic/735 | 1 +
> tests/generic/795 | 2 ++
> 5 files changed, 6 insertions(+)
>
> --
> 2.55.0
>
prev parent reply other threads:[~2026-09-03 13:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 3:53 [PATCH v2 0/3] xfstests: add missing _require_scratch checks Prabhakar Pujeri
2026-09-03 3:53 ` [PATCH v2 1/3] generic/590,735: add missing _require_scratch check Prabhakar Pujeri
2026-09-03 3:53 ` [PATCH v2 2/3] generic/795: " Prabhakar Pujeri
2026-09-03 3:53 ` [PATCH v2 3/3] f2fs/015,016: add missing _require_scratch checks Prabhakar Pujeri
2026-09-03 3:53 ` [f2fs-dev] [PATCH v2 3/3] f2fs/015, 016: " Prabhakar Pujeri via Linux-f2fs-devel
2026-09-03 23:35 ` Chao Yu
2026-09-03 23:35 ` Chao Yu via Linux-f2fs-devel
2026-09-03 13:53 ` Zorro Lang [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=apl53bE5aZMJmZII@zlang-mailbox \
--to=zlang@kernel.org \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=prabhakar.pujeri@dell.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 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.