mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: kernel test robot <lkp@intel.com>, Jonathan Corbet <corbet@lwn.net>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: htmldocs: Documentation/driver-api/tty/tty_port.rst:65: WARNING: Document or section may not begin with a transition. [docutils]
Date: Mon, 2 Feb 2026 13:57:46 -0800	[thread overview]
Message-ID: <0d0b90c1-db32-4eab-98c2-9bb46cea7a8d@infradead.org> (raw)
In-Reply-To: <202602022007.fALe9bGB-lkp@intel.com>

Hi k.t.r.,

On 2/2/26 11:45 AM, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   18f7fcd5e69a04df57b563360b88be72471d6b62
> commit: 00d95fcc4dee66dfb6980de6f2973b32f973a1eb docs: kdoc: handle the obsolescensce of docutils.ErrorString()
> date:   5 months ago
> reproduce: (https://download.01.org/0day-ci/archive/20260202/202602022007.fALe9bGB-lkp@intel.com/reproduce)

I cannot reproduce this warning.
What version of docutils do you use?

> 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/202602022007.fALe9bGB-lkp@intel.com/
> 
> All warnings (new ones prefixed by >>):
> 
>    WARNING: No kernel-doc for file ./include/linux/tty_port.h
>    ERROR: Cannot find file ./include/linux/tty_port.h
>    WARNING: No kernel-doc for file ./include/linux/tty_port.h
>    ERROR: Cannot find file ./include/linux/tty_port.h
>    WARNING: No kernel-doc for file ./include/linux/tty_port.h
>>> Documentation/driver-api/tty/tty_port.rst:65: WARNING: Document or section may not begin with a transition. [docutils]
>    ERROR: Cannot find file ./include/linux/tty.h
>    WARNING: No kernel-doc for file ./include/linux/tty.h
>    ERROR: Cannot find file ./include/linux/tty.h
>    WARNING: No kernel-doc for file ./include/linux/tty.h
>    ERROR: Cannot find file ./include/linux/tty.h
> 
> 
> vim +65 Documentation/driver-api/tty/tty_port.rst
> 
> 3f19fed8d0daed Documentation/tty/tty_port.rst Jiri Slaby 2021-11-26  61  
> 3f19fed8d0daed Documentation/tty/tty_port.rst Jiri Slaby 2021-11-26  62  .. kernel-doc:: include/linux/tty_port.h
> 3f19fed8d0daed Documentation/tty/tty_port.rst Jiri Slaby 2021-11-26  63     :identifiers: tty_port
> 3f19fed8d0daed Documentation/tty/tty_port.rst Jiri Slaby 2021-11-26  64  
> 3f19fed8d0daed Documentation/tty/tty_port.rst Jiri Slaby 2021-11-26 @65  ----
> 3f19fed8d0daed Documentation/tty/tty_port.rst Jiri Slaby 2021-11-26  66  
> 
> :::::: The code at line 65 was first introduced by commit
> :::::: 3f19fed8d0daed6e0e04b130d203d4333b757901 Documentation: add TTY chapter
> 
> :::::: TO: Jiri Slaby <jslaby@suse.cz>
> :::::: CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> 

thanks.
-- 
~Randy


  reply	other threads:[~2026-02-02 21:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-02 19:45 kernel test robot
2026-02-02 21:57 ` Randy Dunlap [this message]
2026-02-06  2:29   ` Oliver Sang

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=0d0b90c1-db32-4eab-98c2-9bb46cea7a8d@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®