From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Zorro Lang <zlang@kernel.org>,
Brian Foster <bfoster@redhat.com>,
fstests@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 3/3] replace _supported_fs with _exclude_fs
Date: Wed, 29 Jan 2025 06:28:59 +0100 [thread overview]
Message-ID: <20250129052859.GA28707@lst.de> (raw)
In-Reply-To: <20250128191958.GR3557695@frogsfrogsfrogs>
On Tue, Jan 28, 2025 at 11:19:58AM -0800, Darrick J. Wong wrote:
> > system is not supported for the common test. For ext4 this increases
> > the existing mess even further, but the maintainers have a plan to
> > move it to feature checks instead that are hopefully easier to
> > understand.
>
> They do? FWIW the tests/ext4 conversions look reasonable as a
> mechanical change to me, but I /was/ wondering what they'd think of this
> change.
Ted mentioned that's the preferred way in reply to v1 after he apparently
brought this up on some ext4 call. I personally still think abusing
the ext4 dir for ext2/3 is stupid, but I don't care strongly enough to
fight.
next prev parent reply other threads:[~2025-01-29 5:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 7:12 remove _supported_fs v2 Christoph Hellwig
2025-01-28 7:12 ` [PATCH 1/3] generic/363: remove _supported_fs xfs Christoph Hellwig
2025-01-28 19:17 ` Darrick J. Wong
2025-01-29 5:26 ` Christoph Hellwig
2025-01-28 7:12 ` [PATCH 2/3] common: remove the $FSYP check in _cleanup_dump Christoph Hellwig
2025-01-28 19:14 ` Darrick J. Wong
2025-01-29 5:27 ` Christoph Hellwig
2025-01-28 7:13 ` [PATCH 3/3] replace _supported_fs with _exclude_fs Christoph Hellwig
2025-01-28 19:19 ` Darrick J. Wong
2025-01-29 5:28 ` Christoph Hellwig [this message]
2025-02-02 13:31 ` Zorro Lang
2025-02-03 6:40 ` Christoph Hellwig
2025-02-04 17:36 ` Zorro Lang
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=20250129052859.GA28707@lst.de \
--to=hch@lst.de \
--cc=bfoster@redhat.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--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 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.