From: Eric Biggers <ebiggers3@gmail.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Eryu Guan <eguan@redhat.com>,
fstests@vger.kernel.org, Eric Biggers <ebiggers@google.com>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH 0/6] xfstests: remove most IRIX-specific code
Date: Thu, 1 Jun 2017 18:25:11 -0700 [thread overview]
Message-ID: <20170602012511.GB612@zzz> (raw)
In-Reply-To: <20170601153347.GG4519@birch.djwong.org>
On Thu, Jun 01, 2017 at 08:33:47AM -0700, Darrick J. Wong wrote:
> On Thu, Jun 01, 2017 at 03:29:02PM +0800, Eryu Guan wrote:
> > On Wed, May 31, 2017 at 08:29:04PM -0700, Eric Biggers wrote:
> > > On Thu, Jun 01, 2017 at 11:12:35AM +0800, Eryu Guan wrote:
> > > > On Wed, May 31, 2017 at 03:36:49PM -0700, Eric Biggers wrote:
> > > > > From: Eric Biggers <ebiggers@google.com>
> > > > >
> > > > > For some time xfstests has de facto not supported IRIX anymore. The
> > > > > final release of IRIX was over 10 years ago and it seems no one has
> > > > > been running the latest xfstests releases on any IRIX system, as at
> > > > > the very least xfstests now assumes the existence of some util-linux
> > > > > binaries. There are probably other examples of this bitrot too.
> > > > >
> > > > > Therefore, this patchset simplifies things removing IRIX support from
> > > > > the xfstests tests, build system, and documentation.
> > > > >
> > > > > It focuses on making larger, more obvious cleanups. Of course,
> > > > > there's more to do if people want to spend more time going through
> > > > > some of the more intricate details, especially XFS-specific details.
> > > > > But this should be a good start.
> > > >
> > > > Thanks a lot for doing this!! I didn't see patch #2 and #3 hit the list
> > > > (too big for the list?). Do you have a public git repo that I can pull
> > > > from?
> > > >
> > >
> > > Ick, I guess the size limit must be 100K. I've pushed the series out to
> > > repository https://github.com/ebiggers/xfstests, branch "remove_irix_support".
> > >
> > > Note that the two biggest patches can be more easily reviewed with
> > > 'git diff -D', since that abbreviates the file deletions.
> >
> > Thanks!
> >
> > I also cc'ed linux-xfs list for review, as IRIX support is mainly for
> > XFS.
>
> I think it's safe to drop IRIX support; xfsprogs dropped it in 4.10.
>
> That said, I also think "tests: remove IRIX-specific tests" removes too
> many tests. generic/097 looks like a fairly generic xattr usage test,
> why not just fix it to work on Linux (and sort the attrs to stabilize
> the output)? Neither of the removed udf tests seem to test anything
> Irix specific; either fix them to work with the Linux udf tools (or kill
> udf/102).
>
> I looked through the rest of the patches in the branch and they looked
> ok to me. Thanks for cleaning out that cruft.
>
> --D
>
Okay, thanks for the review. When I have time I'll look into porting the
removed tests to Linux.
I also noticed there's a small bug in patch 3/6 that broke xfs/073; I'll fix
that in v2. (Also, for easier review I'll probably use 'git format-patch -D' so
the mailing list doesn't eat the larger patches.)
Eric
next prev parent reply other threads:[~2017-06-02 1:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 22:36 [PATCH 0/6] xfstests: remove most IRIX-specific code Eric Biggers
2017-05-31 22:36 ` [PATCH 1/6] README: remove IRIX-specific documentation Eric Biggers
2017-05-31 22:36 ` [PATCH 4/6] tests: clean up per-OS output files Eric Biggers
2017-05-31 22:36 ` [PATCH 5/6] common: remove IRIX-specific code Eric Biggers
2017-05-31 22:36 ` [PATCH 6/6] build: remove IRIX-specific build logic Eric Biggers
2017-06-01 3:12 ` [PATCH 0/6] xfstests: remove most IRIX-specific code Eryu Guan
2017-06-01 3:29 ` Eric Biggers
2017-06-01 7:29 ` Eryu Guan
2017-06-01 15:33 ` Darrick J. Wong
2017-06-02 1:25 ` Eric Biggers [this message]
2017-06-02 2:54 ` Eryu Guan
2017-06-02 3:34 ` Eryu Guan
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=20170602012511.GB612@zzz \
--to=ebiggers3@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=ebiggers@google.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@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.