From: Jan Kara <jack@suse.cz>
To: Christoph Hellwig <hch@lst.de>
Cc: Zorro Lang <zlang@kernel.org>, Brian Foster <bfoster@redhat.com>,
fstests@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 3/4] ext-common: create a new test directory for ext* common tests
Date: Wed, 18 Dec 2024 16:59:47 +0100 [thread overview]
Message-ID: <20241218155947.ocbq6hjdzaud6ioj@quack3> (raw)
In-Reply-To: <20241210065900.1235379-4-hch@lst.de>
On Tue 10-12-24 07:58:27, Christoph Hellwig wrote:
> Split the tests shared with ext2 and ext3 from the ext4 directory.
> This makes ext4 a normal file system specific directory and cuts down
> the number of _supported_fs calls to a little more than a handful
> for tests that can't run on ext2.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
So I went through all ext4 tests and I think:
ext4/004 should work for all ext? types -> move to ext_common
ext4/006 should work for all ext? types -> move to ext_common
ext4/007 should work for all ext? types -> move to ext_common
ext4/008 should work for all ext? types -> move to ext_common
ext4/009 should work for all ext? types -> move to ext_common
ext4/010 should work for all ext? types -> move to ext_common
ext4/011 should work for all ext? types -> move to ext_common
ext4/012 should work for all ext? types -> move to ext_common
ext4/013 should work for all ext? types -> move to ext_common
ext4/014 should work for all ext? types -> move to ext_common
ext4/016 should work for all ext? types -> move to ext_common
- but I've now noticed that the last ten call _scratch_mkfs_ext4
instead of _scratch_mkfs so that would need fixing up. So maybe leave
it as is for now
ext4/017 should work for all ext3 & ext4 types -> move to ext_common
- similar caveat with _scratch_mkfs_ext4
ext4/018 should work for all ext? types -> move to ext_common
ext4/019 should work for all ext? types -> move to ext_common
- similar caveat with _scratch_mkfs_ext4
ext4/022 should work for ext3 & ext4 -> move to ext_common
ext4/023 should work for all ext? types -> move to ext_common
ext4/044 should work for all ext? types -> move to ext_common
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2024-12-18 15:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 6:58 remove _supported_fs Christoph Hellwig
2024-12-10 6:58 ` [PATCH 1/4] generic/363: remove _supported_fs xfs Christoph Hellwig
2024-12-10 13:15 ` Brian Foster
2024-12-10 6:58 ` [PATCH 2/4] common: remove the $FSYP check in _cleanup_dump Christoph Hellwig
2024-12-10 6:58 ` [PATCH 3/4] ext-common: create a new test directory for ext* common tests Christoph Hellwig
2024-12-18 15:59 ` Jan Kara [this message]
2024-12-23 8:38 ` Christoph Hellwig
2024-12-10 6:58 ` [PATCH 4/4] replace _supported_fs with _exclude_fs Christoph Hellwig
2024-12-10 13:00 ` remove _supported_fs Theodore Ts'o
2024-12-10 16:08 ` Christoph Hellwig
2024-12-19 17:02 ` Theodore Ts'o
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=20241218155947.ocbq6hjdzaud6ioj@quack3 \
--to=jack@suse.cz \
--cc=bfoster@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
--cc=linux-ext4@vger.kernel.org \
--cc=zlang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox