linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: zlang@redhat.com, fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/2] xfs/122: add tests for commitrange structures
Date: Tue, 1 Oct 2024 22:45:50 -0700	[thread overview]
Message-ID: <ZvzeDhbIUPEHCP2D@infradead.org> (raw)
In-Reply-To: <172780126049.3586479.7813790327650448381.stgit@frogsfrogsfrogs>

On Tue, Oct 01, 2024 at 09:49:27AM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
> 
> Update this test to check the ioctl structure for XFS_IOC_COMMIT_RANGE.

Meh.  Can we please not add more to xfs/122, as that's alway just
a pain?  We can just static_assert the size in xfsprogs (or the
xfstests code using it) instead of this mess.


  reply	other threads:[~2024-10-02  5:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-01 16:48 [PATCHSET v31.1 2/2] fstests: atomic file content commits Darrick J. Wong
2024-10-01 16:49 ` [PATCH 1/2] src/fiexchange.h: add the start-commit/commit-range ioctls Darrick J. Wong
2024-10-02  5:45   ` Christoph Hellwig
2024-10-01 16:49 ` [PATCH 2/2] xfs/122: add tests for commitrange structures Darrick J. Wong
2024-10-02  5:45   ` Christoph Hellwig [this message]
2024-10-02 22:47     ` Darrick J. Wong
2024-10-03 12:10       ` Christoph Hellwig
2024-10-11  6:28       ` Zorro Lang
2024-10-11 18:19         ` Darrick J. Wong
2024-10-12 14:05           ` Zorro Lang
2024-10-03 21:37 ` [PATCH] fsstress: add support for FALLOC_FL_UNSHARE_RANGE Darrick J. Wong
2024-10-07 13:18   ` Brian Foster
2024-10-11  5:13   ` Zorro Lang
2024-10-11  5:21     ` Zorro Lang
2024-10-11 16:08       ` 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=ZvzeDhbIUPEHCP2D@infradead.org \
    --to=hch@infradead.org \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).