linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Qais Yousef <qyousef@layalina.io>
Cc: oe-kbuild-all@lists.linux.dev, linux-doc@vger.kernel.org
Subject: [qais-yousef:uclamp-max-aggregation 11/11] htmldocs: Documentation/scheduler/sched-util-clamp.rst:172: WARNING: undefined label: schedutil-response-time-issues (if the link has no caption the label must precede a section header)
Date: Thu, 7 Dec 2023 07:20:32 +0800	[thread overview]
Message-ID: <202312070722.6ljjHYA7-lkp@intel.com> (raw)

tree:   https://github.com/qais-yousef/linux uclamp-max-aggregation
head:   125f789d9c871f96dccf78573b6760d24cdebcc8
commit: d3e87a62acb4d2f91799d5112ae868760ab94bfa [11/11] sched/documentation: Remove reference to max aggregation
reproduce: (https://download.01.org/0day-ci/archive/20231207/202312070722.6ljjHYA7-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/202312070722.6ljjHYA7-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> Documentation/scheduler/sched-util-clamp.rst:172: WARNING: undefined label: schedutil-response-time-issues (if the link has no caption the label must precede a section header)

vim +172 Documentation/scheduler/sched-util-clamp.rst

   171	
 > 172	See :ref:`Section 5.1 <schedutil-response-time-issues>` for more details on
   173	schedutil related limitations.
   174	

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

                 reply	other threads:[~2023-12-06 23:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202312070722.6ljjHYA7-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=qyousef@layalina.io \
    /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;
as well as URLs for NNTP newsgroup(s).