mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Omokefe Emmanuel Onanaroghene <emmaonana18@gmail.com>
Cc: ericvh@gmail.com, aneesh.kumar@linux.vnet.ibm.com,
	jvrao@linux.vnet.ibm.com, v9fs@lists.linux.dev,
	linux-kernel@vger.kernel.org, ericvh@kernel.org,
	lucho@ionkov.net, linux_oss@crudebyte.com,
	skhan@linuxfoundation.org
Subject: Re: [PATCH] 9p: fix kernel-doc warning for enum p9_session_flags
Date: Thu, 29 Oct 2026 10:15:35 +0900	[thread overview]
Message-ID: <auKeN8lGQMw5yYJt@codewreck.org> (raw)
In-Reply-To: <20261002035837.39703-1-emmaonana18@gmail.com>

Omokefe Emmanuel Onanaroghene wrote on Fri, Oct 02, 2026 at 04:58:37AM +0100:
> kernel-doc cannot parse enum p9_session_flags, since its documentation
> comment is followed by #define lines instead of the enum declaration:
> 
>   fs/9p/v9fs.h:31 : error: Cannot parse enum!
> 
> Move the three #define lines below the enum whose values they are
> derived from, and give V9FS_ACCESS_ANY and V9FS_ACCESS_MASK their own
> kernel-doc comments with the descriptions they had in the enum comment.
> 
> Also document the four enum members that had no description, using the
> corresponding mount option wording from
> Documentation/filesystems/9p.rst.
> 
> Fixes: 76381a42e4a5 ("fs/9p: Add access = client option to opt in acl evaluation.")
> Assisted-by: LLM
> Signed-off-by: Omokefe Emmanuel Onanaroghene <emmaonana18@gmail.com>

Sure, why not; picked up.

> ---
>  fs/9p/v9fs.h | 26 ++++++++++++++++++--------
>  1 file changed, 18 insertions(+), 8 deletions(-)
> 
> diff --git a/fs/9p/v9fs.h b/fs/9p/v9fs.h
> index a462bcbfc7da..2f18e75f0ed0 100644
> --- a/fs/9p/v9fs.h
> +++ b/fs/9p/v9fs.h
> @@ -21,20 +21,16 @@
>   * @V9FS_ACCESS_SINGLE: only the mounting user can access the hierarchy
>   * @V9FS_ACCESS_USER: a new attach will be issued for every user (default)
>   * @V9FS_ACCESS_CLIENT: Just like user, but access check is performed on client.
> - * @V9FS_ACCESS_ANY: use a single attach for all users
> - * @V9FS_ACCESS_MASK: bit mask of different ACCESS options
>   * @V9FS_POSIX_ACL: POSIX ACLs are enforced
> + * @V9FS_NO_XATTR: do not offer xattr functions on this mount
> + * @V9FS_IGNORE_QV: ignore qid.version==0 as a marker to ignore cache
> + * @V9FS_DIRECT_IO: bypass page cache on all read/write operations
> + * @V9FS_SYNC: flush writes synchronously to the server

I reworded these a bit as 'flush writes' sounded a bit off.

+ * @V9FS_IGNORE_QV: ignore qid.version==0 as a marker to disable data cache
+ * @V9FS_DIRECT_IO: disable data read/write cache
+ * @V9FS_SYNC: disable data write cache

-- 
Dominique Martinet | Asmadeus

      reply	other threads:[~2026-10-29  1:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02  3:58 Omokefe Emmanuel Onanaroghene
2026-10-29  1:15 ` Dominique Martinet [this message]

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=auKeN8lGQMw5yYJt@codewreck.org \
    --to=asmadeus@codewreck.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=emmaonana18@gmail.com \
    --cc=ericvh@gmail.com \
    --cc=ericvh@kernel.org \
    --cc=jvrao@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux_oss@crudebyte.com \
    --cc=lucho@ionkov.net \
    --cc=skhan@linuxfoundation.org \
    --cc=v9fs@lists.linux.dev \
    /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®