From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: zlang@redhat.com, guan@eryu.me, david@fromorbit.com,
fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/2] xfs: test unlinked inode list repair on demand
Date: Wed, 8 Nov 2023 21:39:44 -0800 [thread overview]
Message-ID: <ZUxwoLoy2D/CIUbE@infradead.org> (raw)
In-Reply-To: <169947895967.203694.8763078075817732328.stgit@frogsfrogsfrogs>
> +# Modify as appropriate.
Btw, why do we keep adding this pointless boilerplate everywhere?
> +_supported_fs generic
I think this should be xfs only.
> +source ./common/filter
> +source ./common/fuzzy
> +source ./common/quota
When did we switch from using . to source other shell files
to "source"? Just curious.
> +
> +# real QA test starts here
> +
> +# Modify as appropriate.
> +_supported_fs generic
xfs again.
next prev parent reply other threads:[~2023-11-09 5:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 21:29 [PATCHSET v3 0/2] fstests: reload entire iunlink lists Darrick J. Wong
2023-11-08 21:29 ` [PATCH 1/2] common: make helpers for ttyprintk usage Darrick J. Wong
2023-11-09 5:36 ` Christoph Hellwig
2023-11-08 21:29 ` [PATCH 2/2] xfs: test unlinked inode list repair on demand Darrick J. Wong
2023-11-09 5:39 ` Christoph Hellwig [this message]
2023-11-10 4:46 ` Darrick J. Wong
-- strict thread matches above, loose matches on Subject: below --
2023-11-13 17:08 [PATCHSET v4 0/2] fstests: reload entire iunlink lists Darrick J. Wong
2023-11-13 17:08 ` [PATCH 2/2] xfs: test unlinked inode list repair on demand Darrick J. Wong
2023-11-16 14:42 ` Zorro Lang
2023-11-16 17:30 [PATCHSET v5 0/2] fstests: reload entire iunlink lists Darrick J. Wong
2023-11-16 17:30 ` [PATCH 2/2] xfs: test unlinked inode list repair on demand Darrick J. Wong
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=ZUxwoLoy2D/CIUbE@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@redhat.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