All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Garry <john.g.garry@oracle.com>
To: "Darrick J. Wong" <djwong@kernel.org>, aalbersh@kernel.org
Cc: hch@lst.de, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/5] xfs_io: catch statx fields up to 6.15
Date: Fri, 25 Apr 2025 15:05:36 +0100	[thread overview]
Message-ID: <c77bdf38-cbc4-4c48-8a5b-82e938d7b40d@oracle.com> (raw)
In-Reply-To: <174553149356.1175632.17456557520696046949.stgit@frogsfrogsfrogs>

On 24/04/2025 22:53, Darrick J. Wong wrote:
> From: Darrick J. Wong<djwong@kernel.org>
> 
> Add all the new statx fields and flags that have accumulated for the
> past couple of years so they all print now.
> 
> Signed-off-by: "Darrick J. Wong"<djwong@kernel.org>
> Reviewed-by: Christoph Hellwig<hch@lst.de>

FWIW:
Reviewed-by: John Garry <john.g.garry@oracle.com>

  reply	other threads:[~2025-04-25 14:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-24 21:52 [PATCHSET] xfsprogs: random bug fixes Darrick J. Wong
2025-04-24 21:52 ` [PATCH 1/5] man: fix missing cachestat manpage Darrick J. Wong
2025-04-24 21:53 ` [PATCH 2/5] xfs_io: catch statx fields up to 6.15 Darrick J. Wong
2025-04-25 14:05   ` John Garry [this message]
2025-04-24 21:53 ` [PATCH 3/5] xfs_io: redefine what statx -m all does Darrick J. Wong
2025-04-25 12:23   ` Andrey Albershteyn
2025-04-25 13:11   ` Christoph Hellwig
2025-04-25 14:50     ` Darrick J. Wong
2025-04-25 14:51       ` Christoph Hellwig
2025-04-25 14:24   ` John Garry
2025-04-24 21:53 ` [PATCH 4/5] xfs_io: make statx mask parsing more generally useful Darrick J. Wong
2025-04-25 12:24   ` Andrey Albershteyn
2025-04-25 13:12   ` Christoph Hellwig
2025-04-24 21:53 ` [PATCH 5/5] mkfs: fix blkid probe API violations causing weird output 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=c77bdf38-cbc4-4c48-8a5b-82e938d7b40d@oracle.com \
    --to=john.g.garry@oracle.com \
    --cc=aalbersh@kernel.org \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --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.