mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Al Viro <viro@zeniv.linux.org.uk>
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 13:48:08 +0700	[thread overview]
Message-ID: <aUOjqBtYX-rafsvU@archie.me> (raw)
In-Reply-To: <20251218061056.GX1712166@ZenIV>

[-- Attachment #1: Type: text/plain, Size: 882 bytes --]

On Thu, Dec 18, 2025 at 06:10:56AM +0000, Al Viro wrote:
> The first one might be borderline sane (I'd probably go for O_... instead
> of O_, but whatever); the second is not.

Or O_\* flags?

> 
> 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).

Ack. Will apply your suggestions in v2.

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2025-12-18  6:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-18  5:05 Bagas Sanjaya via B4 Relay
2025-12-18  6:10 ` Al Viro
2025-12-18  6:48   ` Bagas Sanjaya [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=aUOjqBtYX-rafsvU@archie.me \
    --to=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 \
    --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®