From: Al Viro <viro@zeniv.linux.org.uk>
To: bagasdotme@gmail.com
Cc: Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Benjamin Coddington <bcodding@hammerspace.com>,
Jeff Layton <jlayton@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH] VFS: fix dentry_create() kernel-doc comment
Date: Thu, 18 Dec 2025 06:10:56 +0000 [thread overview]
Message-ID: <20251218061056.GX1712166@ZenIV> (raw)
In-Reply-To: <20251218-dentry-inline-v1-1-0107f4cd8246@gmail.com>
On Thu, Dec 18, 2025 at 12:05:00PM +0700, Bagas Sanjaya via B4 Relay wrote:
> @@ -4939,7 +4939,7 @@ EXPORT_SYMBOL(start_creating_user_path);
> /**
> * dentry_create - Create and open a file
> * @path: path to create
> - * @flags: O_ flags
> + * @flags: O\_ flags
> * @mode: mode bits for new file
> * @cred: credentials to use
> *
> @@ -4950,7 +4950,7 @@ EXPORT_SYMBOL(start_creating_user_path);
> * the new file is to be created. The parent directory and the
> * negative dentry must reside on the same filesystem instance.
> *
> - * On success, returns a "struct file *". Otherwise a ERR_PTR
> + * On success, returns a "struct file \*". Otherwise a ERR_PTR
> * is returned.
> */
The first one might be borderline sane (I'd probably go for O_... instead
of O_, but whatever); the second is not.
Forget kernel-doc; what is that phrase supposed to mean in the
first place? "struct file *" (in quotes, for whatever reason)
would presumably imply a value of mentioned type; a function
declared as
struct file *dentry_create(const struct path *path, int flags, umode_t mode,
const struct cred *cred)
*always* returns a value of that type, TYVM.
I'm not a native speaker, but I'd suggest something along the lines
of "a pointer to opened file" as replacement for that (without
quote marks, obviously).
next prev parent reply other threads:[~2025-12-18 6:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 5:05 [PATCH] VFS: fix dentry_create() kernel-doc comment Bagas Sanjaya via B4 Relay
2025-12-18 6:10 ` Al Viro [this message]
2025-12-18 6:48 ` Bagas Sanjaya
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=20251218061056.GX1712166@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=bagasdotme@gmail.com \
--cc=bcodding@hammerspace.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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