public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Zorro Lang <zlang@kernel.org>
Cc: Brian Foster <bfoster@redhat.com>,
	fstests@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: remove _supported_fs v2
Date: Tue, 28 Jan 2025 08:12:57 +0100	[thread overview]
Message-ID: <20250128071315.676272-1-hch@lst.de> (raw)

Hi all,

this series removes the remaining _supported_fs calls and replaces them
with a new _exclude_fs call.

The first patch removes a _supported_fs for a relatively new test from
Brian that fails on other file systems.  We should still run it so that
people have a chance to fix the corruption, so I think this make sense.

Unlike the previous version this does not add a new ext-common directory,
but instead uses _exclude_fs for those tests as well, which doesn't
look quite as nice.  Some of the ext4 maintainers said they might want
to switch this to feature checks, which sounds great but also something
better done by people familiar with extN.

Changes since v1:
 - remove the separated ext-common directory previously added

             reply	other threads:[~2025-01-28  7:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-28  7:12 Christoph Hellwig [this message]
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
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=20250128071315.676272-1-hch@lst.de \
    --to=hch@lst.de \
    --cc=bfoster@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox