Linux Documentation
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: kernel test robot <lkp@intel.com>,
	Benjamin Coddington <bcodding@hammerspace.com>
Cc: oe-kbuild-all@lists.linux.dev,
	Christian Brauner <brauner@kernel.org>,
	Jeff Layton <jlayton@kernel.org>,
	linux-doc@vger.kernel.org
Subject: Re: [linux-next:master 1503/2671] htmldocs: Documentation/filesystems/api-summary:56: ./fs/namei.c:4953: WARNING: Inline emphasis start-string without end-string. [docutils]
Date: Thu, 1 Jan 2026 19:36:48 -0800	[thread overview]
Message-ID: <745448ec-d69f-4f0c-ac02-08c5d757569f@infradead.org> (raw)
In-Reply-To: <202601011410.4vVaIDB9-lkp@intel.com>

Benjamin,

On 1/1/26 5:27 AM, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head:   cc3aa43b44bdb43dfbac0fcb51c56594a11338a8
> commit: 977de00dfcf87e8d95f55dfc247955dc2f9da14d [1503/2671] VFS: move dentry_create() from fs/open.c to fs/namei.c
> reproduce: (https://download.01.org/0day-ci/archive/20260101/202601011410.4vVaIDB9-lkp@intel.com/reproduce)
> 
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202601011410.4vVaIDB9-lkp@intel.com/
> 
> All warnings (new ones prefixed by >>):
> 
>    ERROR: Cannot find file ./include/linux/dcache.h
>    WARNING: No kernel-doc for file ./include/linux/dcache.h
>    WARNING: ./fs/inode.c:1607 function parameter 'isnew' not described in 'ilookup5_nowait'
>    WARNING: ./fs/namei.c:2853 function parameter 'state' not described in '__start_dirop'
>    WARNING: ./fs/namei.c:2853 expecting prototype for start_dirop(). Prototype was for __start_dirop() instead
>>> Documentation/filesystems/api-summary:56: ./fs/namei.c:4953: WARNING: Inline emphasis start-string without end-string. [docutils]
>    Documentation/filesystems/api-summary:56: ./fs/namei.c:4943: ERROR: Unknown target name: "o". [docutils]
>    ERROR: Cannot find file ./include/linux/buffer_head.h
>    WARNING: No kernel-doc for file ./include/linux/buffer_head.h
>    ERROR: Cannot find file ./include/linux/fscache-cache.h
>    WARNING: No kernel-doc for file ./include/linux/fscache-cache.h

fs/open.c is not used in Documentation/ (where the lines were moved _from_).

fs/namei.c needs changes like:

---
 fs/namei.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

--- linux-next-20251219.orig/fs/namei.c
+++ linux-next-20251219/fs/namei.c
@@ -4938,7 +4938,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
  *
@@ -4949,7 +4949,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.
  */
 struct file *dentry_create(struct path *path, int flags, umode_t mode,


Or                         &struct file \*.
without the quotation marks.

-- 
~Randy


  reply	other threads:[~2026-01-02  3:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-01 13:27 [linux-next:master 1503/2671] htmldocs: Documentation/filesystems/api-summary:56: ./fs/namei.c:4953: WARNING: Inline emphasis start-string without end-string. [docutils] kernel test robot
2026-01-02  3:36 ` Randy Dunlap [this message]
2026-01-02  3:44   ` Matthew Wilcox
2026-01-02  6:38     ` Randy Dunlap
2026-01-05 23:59   ` Gopi Krishna Menon

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=745448ec-d69f-4f0c-ac02-08c5d757569f@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=bcodding@hammerspace.com \
    --cc=brauner@kernel.org \
    --cc=jlayton@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@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