From: Dave Chinner <david@fromorbit.com>
To: fstests@vger.kernel.org
Subject: Re: [PATCH 00/13 V2] fstests: fixes and more fixes...
Date: Wed, 18 May 2022 07:39:18 +1000 [thread overview]
Message-ID: <20220517213918.GP2306852@dread.disaster.area> (raw)
In-Reply-To: <20220517082409.anf5f5wg3yoldpki@zlang-mailbox>
On Tue, May 17, 2022 at 04:24:09PM +0800, Zorro Lang wrote:
> On Tue, May 17, 2022 at 05:49:10PM +1000, Dave Chinner wrote:
> > On Tue, May 17, 2022 at 05:00:59PM +1000, Dave Chinner wrote:
> > > Hi folks,
> > >
> > > This is a rollup of the two patch series I sent yesterday titled:
> > >
> > > [PATCH 0/3] fstests: test updates for XFS 5.19 kernel mods
> > > [PATCH 0/3] fstests: more fixes...
> > >
> > > I've fixed some patches, added documentation for those changes,
> > > and added a bunch of patches to remove deprecated/broken tests that
> > > should ahve been removed long ago.
> > >
> > > I do not know if patches 9-11 will make it through vger this time -
> > > they didn't as a single patch. They are titled:
>
> No, they didn't.
>
> > >
> > > [PATCH 09/12] xfs/018: remove deprecated test
> > > [PATCH 10/12] xfs/081: remove deprecated test
> > > [PATCH 11/12] xfs/082: remove deprecated test
> > >
> > > and is thould be pretty obvious what they do from the title....
> >
> > Ok, it appears as though even separated vger still won't let a
> > single one of them through
> >
> > Zorro, all these patches are 'git rm' commands
> >
> > git rm tests/xfs/018*
> > git commit
> > git rm tests/xfs/081*
> > git commit
> > git rm tests/xfs/082*
> > git commit
> >
> > I'm happy for you to just run them yourself, or do you want me to
> > send a pull request for them?
>
> Sure, I don't run this 3 cases either. As they're xfs specific cases, so if both
> of you and Darrick agree to remove them entirely, I'm glad to help that :)
>
> And how about remove them in single one commit/patch? Likes:
> ---
> [PATCH] fstests: remove xfs deprecated test
>
> Remove xfs/018, xfs/081 and xfs/082 entirely, as they're deprecated
> and obsolete for long time.
> ---
Fine by me. That's exactly what the first patch I attempted to send
was.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2022-05-17 21:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 7:00 [PATCH 00/13 V2] fstests: fixes and more fixes Dave Chinner
2022-05-17 7:01 ` [PATCH 01/12] fstests: filter quota warnings Dave Chinner
2022-05-17 7:01 ` [PATCH 02/12] xfs/122: add attribute log formats to test output Dave Chinner
2022-05-17 7:01 ` [PATCH 03/12] xfs/348: golden output is not correct Dave Chinner
2022-05-17 7:01 ` [PATCH 04/12] fstests: fix group list generation for whacky test names Dave Chinner
2022-05-19 18:52 ` Darrick J. Wong
2022-05-20 8:36 ` Zorro Lang
2022-05-20 8:54 ` Zorro Lang
2022-05-20 9:25 ` Zorro Lang
2022-05-20 16:23 ` Darrick J. Wong
2022-05-21 0:27 ` Zorro Lang
2022-05-17 7:01 ` [PATCH 05/12] README: document _begin_fstests better Dave Chinner
2022-05-19 23:13 ` Darrick J. Wong
2022-05-20 1:58 ` Dave Chinner
2022-05-20 2:02 ` Darrick J. Wong
2022-05-20 5:23 ` Zorro Lang
2022-05-20 5:42 ` Dave Chinner
2022-05-20 6:16 ` Zorro Lang
2022-05-17 7:01 ` [PATCH 06/12] xfs/148: make test debuggable Dave Chinner
2022-05-19 18:55 ` Darrick J. Wong
2022-05-17 7:01 ` [PATCH 07/12] xfs/148: fix failure from bad shortform size assumptions Dave Chinner
2022-05-20 7:34 ` Zorro Lang
2022-05-21 23:22 ` Dave Chinner
2022-05-17 7:01 ` [PATCH 08/12] generic/081: don't run on DAX capable devices Dave Chinner
2022-05-18 5:11 ` Dave Chinner
2022-05-17 7:01 ` [PATCH 12/12] xfs/191: remove broken test Dave Chinner
2022-05-19 18:55 ` Darrick J. Wong
2022-05-17 7:49 ` [PATCH 00/13 V2] fstests: fixes and more fixes Dave Chinner
2022-05-17 8:24 ` Zorro Lang
2022-05-17 21:39 ` Dave Chinner [this message]
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=20220517213918.GP2306852@dread.disaster.area \
--to=david@fromorbit.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 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.