From: David Howells <dhowells@redhat.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: dhowells@redhat.com, linux-fsdevel@vger.kernel.org,
lczerner@redhat.com, bxue@redhat.com, ceph-devel@vger.kernel.org,
linux-nfs@vger.kernel.org, linux-afs@lists.infradead.org,
linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-btrfs@vger.kernel.org, Jeff Layton <jlayton@redhat.com>
Subject: Re: [RFC PATCH 1/4] vfs: report change attribute in statx for IS_I_VERSION inodes
Date: Fri, 05 Aug 2022 20:17:01 +0100 [thread overview]
Message-ID: <3731056.1659727021@warthog.procyon.org.uk> (raw)
In-Reply-To: <20220805183543.274352-2-jlayton@kernel.org>
Jeff Layton <jlayton@kernel.org> wrote:
> + __u64 stx_chgattr; /* Inode change attribute */
Why not call it stx_change_attr?
David
next prev parent reply other threads:[~2022-08-05 19:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 18:35 [RFC PATCH 0/4] vfs: allow querying i_version via statx Jeff Layton
2022-08-05 18:35 ` [RFC PATCH 1/4] vfs: report change attribute in statx for IS_I_VERSION inodes Jeff Layton
2022-08-05 19:17 ` David Howells [this message]
2022-08-05 20:00 ` Jeff Layton
2022-08-05 22:01 ` Dave Chinner
2022-08-05 22:06 ` Jeff Layton
2022-08-08 13:19 ` Jeff Layton
2022-08-09 15:33 ` Darrick J. Wong
2022-08-09 18:04 ` Jeff Layton
2022-08-09 18:28 ` Jeff Layton
2022-08-08 2:09 ` Xiubo Li
2022-08-08 10:18 ` Jeff Layton
2022-08-10 3:00 ` JunChao Sun
2022-08-10 10:35 ` Jeff Layton
2022-08-05 18:35 ` [RFC PATCH 2/4] nfs: report the change attribute if requested Jeff Layton
2022-08-05 18:35 ` [RFC PATCH 3/4] afs: fill out change attribute in statx replies Jeff Layton
2022-08-05 18:35 ` [RFC PATCH 4/4] ceph: fill in the change attribute in statx requests Jeff Layton
2022-08-08 11:56 ` Xiubo Li
2022-08-05 18:52 ` [RFC PATCH 0/4] vfs: allow querying i_version via statx Frank Filz
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=3731056.1659727021@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=bxue@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=jlayton@kernel.org \
--cc=jlayton@redhat.com \
--cc=lczerner@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox