From: Christian Brauner <brauner@kernel.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Kent Overstreet <kent.overstreet@linux.dev>,
linux-fsdevel@vger.kernel.org, linux-btrfs@vger.kernel.org,
Jan Kara <jack@suse.cz>, Dave Chinner <dchinner@redhat.com>,
"Darrick J. Wong" <djwong@kernel.org>,
Theodore Ts'o <tytso@mit.edu>,
linux-fsdevel@vger.kernel.or
Subject: Re: [PATCH v3 3/7] fs: FS_IOC_GETUUID
Date: Thu, 8 Feb 2024 10:44:00 +0100 [thread overview]
Message-ID: <20240208-allenfalls-abfuhr-a6a815da4e93@brauner> (raw)
In-Reply-To: <CAOQ4uxi-nBzm+h0MkF_P8Efe9tA1q72kBWPWZsrd+owHTf8enQ@mail.gmail.com> <CAOQ4uxhroGgtbXuhoSzk6tMRML4QnVpbvsFcikdLZxR7+ATrkQ@mail.gmail.com>
> Please move that to the end of FS_IOC_* ioctls block.
Done by me during applying.
> typo in list address.
Fixed.
next prev parent reply other threads:[~2024-02-08 9:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 2:56 [PATCH v3 0/7] filesystem visibililty ioctls Kent Overstreet
2024-02-07 2:56 ` [PATCH v3 1/7] fs: super_set_uuid() Kent Overstreet
2024-02-08 10:11 ` Christian Brauner
2024-02-07 2:56 ` [PATCH v3 2/7] overlayfs: Convert to super_set_uuid() Kent Overstreet
2024-02-07 2:56 ` [PATCH v3 3/7] fs: FS_IOC_GETUUID Kent Overstreet
2024-02-07 6:41 ` Amir Goldstein
2024-02-07 6:46 ` Amir Goldstein
2024-02-08 9:44 ` Christian Brauner [this message]
2024-02-07 2:56 ` [PATCH v3 4/7] fat: Hook up sb->s_uuid Kent Overstreet
2024-02-07 2:56 ` [PATCH v3 5/7] fs: FS_IOC_GETSYSFSNAME Kent Overstreet
2024-02-08 10:09 ` Christian Brauner
2024-02-07 2:56 ` [PATCH v3 6/7] xfs: add support for FS_IOC_GETSYSFSNAME Kent Overstreet
2024-02-07 2:56 ` [PATCH v3 7/7] bcachefs: " Kent Overstreet
2024-02-08 10:20 ` [PATCH v3 0/7] filesystem visibililty ioctls Christian Brauner
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=20240208-allenfalls-abfuhr-a6a815da4e93@brauner \
--to=brauner@kernel.org \
--cc=amir73il@gmail.com \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=jack@suse.cz \
--cc=kent.overstreet@linux.dev \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.or \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).