From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: David Howells <dhowells@redhat.com>
Cc: Eric Biggers <ebiggers@kernel.org>,
tytso@mit.edu, adilger.kernel@dilger.ca,
linux-ext4@vger.kernel.org
Subject: Re: Exporting ext4-specific information through fsinfo attributes
Date: Wed, 22 Jul 2020 08:25:50 -0700 [thread overview]
Message-ID: <20200722152550.GA7625@magnolia> (raw)
In-Reply-To: <701163.1595407986@warthog.procyon.org.uk>
On Wed, Jul 22, 2020 at 09:53:06AM +0100, David Howells wrote:
> Darrick J. Wong <darrick.wong@oracle.com> wrote:
>
> > Where are these FSINFO_FEAT* constants defined, and where are they
> > documented?
> >
> > This generally looks ok to me, but I would like to see documentation
> > first.
>
> Have a look at this branch:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=fsinfo-core
>
> Patch "fsinfo: Provide a bitmap of supported features"
>
> https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/commit/?h=fsinfo-core&id=9d7651e966331f18c7bfe053237b3627585c3e79
>
> Documentation:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/commit/?h=fsinfo-core&id=6bb357c42c96c2a5d72ff02d109ce49bd0c455ab
Ah, thank you. The ext4 bits look ok to me.
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
(Looking forward to whenever you get to xfs... :))
--D
> David
>
next prev parent reply other threads:[~2020-07-22 15:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 7:39 Exporting ext4-specific information through fsinfo attributes David Howells
2020-04-01 15:18 ` Darrick J. Wong
2020-04-21 16:17 ` David Howells
2020-04-21 22:07 ` Andreas Dilger
2020-04-22 14:27 ` David Howells
2020-04-22 16:12 ` Darrick J. Wong
2020-07-21 9:20 ` David Howells
2020-07-21 15:37 ` Darrick J. Wong
2020-07-21 15:42 ` Darrick J. Wong
2020-07-22 8:53 ` David Howells
2020-07-22 15:25 ` Darrick J. Wong [this message]
2020-04-01 16:27 ` Eric Biggers
2020-04-01 19:05 ` Darrick J. Wong
2020-04-01 19:28 ` Eric Biggers
2020-04-01 20:36 ` Eric Biggers
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=20200722152550.GA7625@magnolia \
--to=darrick.wong@oracle.com \
--cc=adilger.kernel@dilger.ca \
--cc=dhowells@redhat.com \
--cc=ebiggers@kernel.org \
--cc=linux-ext4@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 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.