public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Thomas Böhler" <witcher@wiredspace.de>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Shuah Khan" <skhan@linuxfoundation.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-doc@vger.kernel.org,
	"Thomas Böhler" <witcher@wiredspace.de>
Subject: Re: [PATCH] docs: filesystems: ensure proc pid substitutable is complete
Date: Sat, 31 Jan 2026 01:38:15 +0100	[thread overview]
Message-ID: <202601310140.l1CiA2nu-lkp@intel.com> (raw)
In-Reply-To: <20260130-ksm_stat-v1-1-a6aa0da78de6@wiredspace.de>

Hi Thomas,

kernel test robot noticed the following build warnings:

[auto build test WARNING on 6b8edfcd661b569f077cc1ea1f7463ec38547779]

url:    https://github.com/intel-lab-lkp/linux/commits/Thomas-B-hler/docs-filesystems-ensure-proc-pid-substitutable-is-complete/20260130-232903
base:   6b8edfcd661b569f077cc1ea1f7463ec38547779
patch link:    https://lore.kernel.org/r/20260130-ksm_stat-v1-1-a6aa0da78de6%40wiredspace.de
patch subject: [PATCH] docs: filesystems: ensure proc pid substitutable is complete
reproduce: (https://download.01.org/0day-ci/archive/20260131/202601310140.l1CiA2nu-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/202601310140.l1CiA2nu-lkp@intel.com/

All warnings (new ones prefixed by >>):

   ERROR: Cannot find file ./include/linux/jbd2.h
   ERROR: Cannot find file ./include/linux/jbd2.h
   WARNING: No kernel-doc for file ./include/linux/jbd2.h
   ERROR: Cannot find file ./include/linux/netfs.h
   WARNING: No kernel-doc for file ./include/linux/netfs.h
>> Documentation/filesystems/proc.rst:2293: WARNING: Title underline too short.
--
   3.14 /proc/<pid>/ksm_stat - Information about the process's ksm status
   --------------------------------------------------------------------- [docutils]
>> Documentation/filesystems/proc.rst:2293: WARNING: Title underline too short.


vim +2293 Documentation/filesystems/proc.rst

f1f1f2569901ec Ivan Babrou   2022-09-22  2291  
d5424c31b9e465 Thomas Böhler 2026-01-30  2292  3.14 /proc/<pid>/ksm_stat - Information about the process's ksm status
91fe0e4d044044 Andrew Morton 2025-01-10 @2293  ---------------------------------------------------------------------
3ab76c767bc783 xu xin        2025-01-10  2294  When CONFIG_KSM is enabled, each process has this file which displays
3ab76c767bc783 xu xin        2025-01-10  2295  the information of ksm merging status.
3ab76c767bc783 xu xin        2025-01-10  2296  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

      parent reply	other threads:[~2026-01-31  0:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-30 15:25 [PATCH] docs: filesystems: ensure proc pid substitutable is complete Thomas Böhler
2026-01-30 18:45 ` Randy Dunlap
2026-01-31  0:38 ` kernel test robot [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=202601310140.l1CiA2nu-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=skhan@linuxfoundation.org \
    --cc=witcher@wiredspace.de \
    /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