From: kernel test robot <lkp@intel.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, Hans Verkuil <hverkuil@xs4all.nl>,
linux-doc@vger.kernel.org
Subject: [mchehab-media-next:master 323/358] htmldocs: Documentation/output/videodev2.h.rst:6: WARNING: undefined label: v4l2-colorspace-last (if the link has no caption the label must precede a section header)
Date: Sat, 16 Jul 2022 11:52:57 +0800 [thread overview]
Message-ID: <202207161116.S0RCaz3D-lkp@intel.com> (raw)
tree: git://linuxtv.org/mchehab/media-next.git master
head: ca24fef0f2c857b0533f21f9a8a756f9e73d60fb
commit: 718d2153ad0de0c7c0b6891eaa7f9918d68b6d5e [323/358] media: v4l2: Make colorspace validity checks more future-proof
reproduce: make htmldocs
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> Documentation/output/videodev2.h.rst:6: WARNING: undefined label: v4l2-colorspace-last (if the link has no caption the label must precede a section header)
>> Documentation/output/videodev2.h.rst:6: WARNING: undefined label: v4l2-xfer-func-last (if the link has no caption the label must precede a section header)
>> Documentation/output/videodev2.h.rst:6: WARNING: undefined label: v4l2-ycbcr-enc-last (if the link has no caption the label must precede a section header)
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-07-16 3:54 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=202207161116.S0RCaz3D-lkp@intel.com \
--to=lkp@intel.com \
--cc=hverkuil@xs4all.nl \
--cc=kbuild-all@lists.01.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
/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