From: Matthew Wilcox <willy@infradead.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-fsdevel@vger.kernel.org, patches@lists.linux.dev,
Christoph Hellwig <hch@lst.de>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] fiemap: use kernel-doc includes in fiemap docbook
Date: Tue, 19 Nov 2024 19:04:39 +0000 [thread overview]
Message-ID: <ZzzhR3QXRBtNJwJb@casper.infradead.org> (raw)
In-Reply-To: <20241119185507.102454-1-rdunlap@infradead.org>
On Tue, Nov 19, 2024 at 10:55:07AM -0800, Randy Dunlap wrote:
> Add some kernel-doc notation to structs in fiemap header files
> then pull that into Documentation/filesystems/fiemap.rst
> instead of duplicating the header file structs in fiemap.rst.
> This helps to future-proof fiemap.rst against struct changes.
Thanks! This is great. Feels free to ignore every suggestion I'm about
to make.
> +/**
> + * struct fiemap_extent - description of one fiemap extent
> + * @fe_logical: logical offset in bytes for the start of the extent
> + * from the beginning of the file
* @fe_logical: Byte offset of extent in the file.
> + * @fe_physical: physical offset in bytes for the start of the extent
> + * from the beginning of the disk
* @fe_physical: Byte offset of extent on disk.
> +/**
> + * struct fiemap - file extent mappings
> + * @fm_start: logical offset (inclusive) at
> + * which to start mapping (in)
Do we want to say "Byte offset"?
>
> +/* flags used in fm_flags: */
> #define FIEMAP_FLAG_SYNC 0x00000001 /* sync file data before map */
> #define FIEMAP_FLAG_XATTR 0x00000002 /* map extended attribute tree */
> #define FIEMAP_FLAG_CACHE 0x00000004 /* request caching of the extents */
>
> #define FIEMAP_FLAGS_COMPAT (FIEMAP_FLAG_SYNC | FIEMAP_FLAG_XATTR)
Do we want to turn this into an enum so it can be kernel-doc?
> +/* flags used in fe_flags: */
> #define FIEMAP_EXTENT_LAST 0x00000001 /* Last extent in file. */
> #define FIEMAP_EXTENT_UNKNOWN 0x00000002 /* Data location unknown. */
> #define FIEMAP_EXTENT_DELALLOC 0x00000004 /* Location still pending.
Likewise
next prev parent reply other threads:[~2024-11-19 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 18:55 [PATCH] fiemap: use kernel-doc includes in fiemap docbook Randy Dunlap
2024-11-19 19:04 ` Matthew Wilcox [this message]
2024-11-19 19:12 ` Randy Dunlap
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=ZzzhR3QXRBtNJwJb@casper.infradead.org \
--to=willy@infradead.org \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=rdunlap@infradead.org \
--cc=viro@zeniv.linux.org.uk \
/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