From: Jeff Layton <jlayton@kernel.org>
To: "André Almeida" <andrealmeid@igalia.com>,
"Chuck Lever" <chuck.lever@oracle.com>,
"Amir Goldstein" <amir73il@gmail.com>,
NeilBrown <neil@brown.name>,
"Olga Kornievskaia" <okorniev@redhat.com>,
"Dai Ngo" <Dai.Ngo@oracle.com>, "Tom Talpey" <tom@talpey.com>,
"Trond Myklebust" <trondmy@kernel.org>,
"Anna Schumaker" <anna@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Christian Brauner" <brauner@kernel.org>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"Jan Kara" <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-dev@igalia.com
Subject: Re: [PATCH 0/4] exportfs: Some kernel-doc fixes
Date: Tue, 13 Jan 2026 06:19:20 -0500 [thread overview]
Message-ID: <45115f6f2acbe9f498b94b1fbf8133ef0052053a.camel@kernel.org> (raw)
In-Reply-To: <20260112-tonyk-fs_uuid-v1-0-acc1889de772@igalia.com>
On Mon, 2026-01-12 at 22:51 -0300, André Almeida wrote:
> This short series removes some duplicated documentation and address some
> kernel-doc issues:
>
> WARNING: ../include/linux/exportfs.h:289 struct member 'get_uuid' not described in 'export_operations'
> WARNING: ../include/linux/exportfs.h:289 struct member 'map_blocks' not described in 'export_operations'
> WARNING: ../include/linux/exportfs.h:289 struct member 'commit_blocks' not described in 'export_operations'
> WARNING: ../include/linux/exportfs.h:289 struct member 'permission' not described in 'export_operations'
> WARNING: ../include/linux/exportfs.h:289 struct member 'open' not described in 'export_operations'
> WARNING: ../include/linux/exportfs.h:289 struct member 'flags' not described in 'export_operations'
>
> ---
> André Almeida (4):
> exportfs: Fix kernel-doc output for get_name()
> exportfs: Mark struct export_operations functions at kernel-doc
> exportfs: Complete kernel-doc for struct export_operations
> docs: exportfs: Use source code struct documentation
>
> Documentation/filesystems/nfs/exporting.rst | 42 ++++-------------------------
> include/linux/exportfs.h | 33 ++++++++++++++++-------
> 2 files changed, 28 insertions(+), 47 deletions(-)
> ---
> base-commit: 9c7ef209cd0f7c1a92ed61eed3e835d6e4abc66c
> change-id: 20260112-tonyk-fs_uuid-973d5fdfc76f
>
> Best regards,
LGTM:
Reviewed-by: Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2026-01-13 11:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 1:51 André Almeida
2026-01-13 1:51 ` [PATCH 1/4] exportfs: Fix kernel-doc output for get_name() André Almeida
2026-01-13 1:51 ` [PATCH 2/4] exportfs: Mark struct export_operations functions at kernel-doc André Almeida
2026-01-13 1:51 ` [PATCH 3/4] exportfs: Complete kernel-doc for struct export_operations André Almeida
2026-01-13 1:51 ` [PATCH 4/4] docs: exportfs: Use source code struct documentation André Almeida
2026-01-13 3:33 ` [PATCH 0/4] exportfs: Some kernel-doc fixes Chuck Lever
2026-01-13 8:45 ` Christian Brauner
2026-01-13 11:19 ` Jeff Layton [this message]
2026-01-14 1:16 ` 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=45115f6f2acbe9f498b94b1fbf8133ef0052053a.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=amir73il@gmail.com \
--cc=andrealmeid@igalia.com \
--cc=anna@kernel.org \
--cc=brauner@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=corbet@lwn.net \
--cc=jack@suse.cz \
--cc=kernel-dev@igalia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=tom@talpey.com \
--cc=trondmy@kernel.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
all inboxes | Powered by JetHome®