FS/XFS testing framework
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: David Sterba <dsterba@suse.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH 1/4] Move shared/032 to generic/740
Date: Wed, 8 May 2024 22:40:07 -0700	[thread overview]
Message-ID: <Zjxht5OKsau5QJYm@infradead.org> (raw)
In-Reply-To: <8dcb7d564180452eec0c2888740c1b0919e171d3.1715108589.git.dsterba@suse.com>

On Tue, May 07, 2024 at 09:07:36PM +0200, David Sterba wrote:
> The shared/ directory was supposed to host tests that apply to a subset
> of all supported filesystems but this is not utilized much and creates a
> split from the generic tests. Move the test to generic.

While we're at it, can we please have a

_have_mkfs_overwrite detetion instead of hardcoding ext4 and btrfs
with another check for that is supported for btrfs?

I'm also pretty sure at least ext4 supports overwrite detection as
well..


  parent reply	other threads:[~2024-05-09  5:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-07 19:07 [PATCH 0/4] Move test cased from shared to generic David Sterba
2024-05-07 19:07 ` [PATCH 1/4] Move shared/032 to generic/740 David Sterba
2024-05-07 22:38   ` Darrick J. Wong
2024-05-09  5:40   ` Christoph Hellwig [this message]
2024-05-09 10:00     ` Zorro Lang
2024-05-09 12:41       ` Christoph Hellwig
2024-05-07 19:07 ` [PATCH 2/4] Move shared/002 to generic/745 David Sterba
2024-05-09  5:40   ` Christoph Hellwig
2024-05-09 16:34     ` David Sterba
2024-05-07 19:07 ` [PATCH 3/4] Move shared/298 to generic/746 David Sterba
2024-05-09  5:41   ` Christoph Hellwig
2024-05-07 19:07 ` [PATCH 4/4] Remove rest of shared/ David Sterba
2024-05-07 22:39 ` [PATCH 0/4] Move test cased from shared to generic Darrick J. Wong
2024-05-09  5:29 ` Zorro Lang
2024-05-09 16:28   ` David Sterba
2024-05-10  1:43     ` 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=Zjxht5OKsau5QJYm@infradead.org \
    --to=hch@infradead.org \
    --cc=dsterba@suse.com \
    --cc=fstests@vger.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