public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: zlang@redhat.com, hch@lst.de, fstests@vger.kernel.org,
	linux-xfs@vger.kernel.org, guan@eryu.me
Subject: Re: [PATCHSET v27.0 0/2] fstests: FIEXCHANGE is now an XFS ioctl
Date: Thu, 9 Nov 2023 06:21:06 +0100	[thread overview]
Message-ID: <20231109052106.GA29241@lst.de> (raw)
In-Reply-To: <169947992096.220003.8427995158013553083.stgit@frogsfrogsfrogs>

On Wed, Nov 08, 2023 at 01:45:20PM -0800, Darrick J. Wong wrote:
> This has been running on the djcloud for months with no problems.  Enjoy!
> Comments and questions are, as always, welcome.

Isn't the branch all new?

Anyway, this fixes skipping the tests when not supported, and runs them
fine when supported:

Reviewed-by: Christoph Hellwig <hch@lst.de>
Tested-by: Christoph Hellwig <hch@lst.de>

although I wonder a bit if keeping functionality not actually supported
upstream in upstream xfstests is such a good idea.  Keeping it in
a development branch for the feature seems more flexible to me.  I guess
there is no point doing a forth and back for this one now, but maybe
should be more careful in the future.

  parent reply	other threads:[~2023-11-09  5:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08 21:45 [PATCHSET v27.0 0/2] fstests: FIEXCHANGE is now an XFS ioctl Darrick J. Wong
2023-11-08 21:45 ` [PATCH 1/2] misc: privatize the FIEXCHANGE ioctl for now Darrick J. Wong
2023-11-16 15:14   ` Zorro Lang
2023-11-16 16:35     ` Darrick J. Wong
2023-11-08 21:45 ` [PATCH 2/2] misc: update xfs_io swapext usage Darrick J. Wong
2023-11-09  5:21 ` Christoph Hellwig [this message]
2023-11-10  4:48   ` [PATCHSET v27.0 0/2] fstests: FIEXCHANGE is now an XFS ioctl Darrick J. Wong

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=20231109052106.GA29241@lst.de \
    --to=hch@lst.de \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=guan@eryu.me \
    --cc=linux-xfs@vger.kernel.org \
    --cc=zlang@redhat.com \
    /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