From: kernel test robot <lkp@intel.com>
To: Satish Kumar Nagireddy <satish.nagireddy.nagireddy@xilinx.com>
Cc: oe-kbuild-all@lists.linux.dev, git@amd.com,
Michal Simek <monstr@monstr.eu>, Hyun Kwon <hyun.kwon@xilinx.com>,
linux-doc@vger.kernel.org
Subject: [xilinx-xlnx:xlnx_rebase_v6.1_LTS 324/1370] htmldocs: Documentation/output/videodev2.h.rst:6: WARNING: undefined label: v4l2-pix-fmt-x412 (if the link has no caption the label must precede a section header)
Date: Tue, 3 Oct 2023 07:40:43 +0800 [thread overview]
Message-ID: <202310030701.UDDAgW9b-lkp@intel.com> (raw)
tree: https://github.com/Xilinx/linux-xlnx xlnx_rebase_v6.1_LTS
head: a19da02cf5b44420ec6afb1eef348c21d9e8cda2
commit: ef3a83b17afa47841de0c22696a1da2c8def1ac3 [324/1370] media: v4l2-ioctl: Add YUV444 12bit and 16bit pixel formats
reproduce: (https://download.01.org/0day-ci/archive/20231003/202310030701.UDDAgW9b-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/202310030701.UDDAgW9b-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Documentation/output/videodev2.h.rst:6: WARNING: undefined label: v4l2-pix-fmt-x412 (if the link has no caption the label must precede a section header)
>> Documentation/output/videodev2.h.rst:6: WARNING: undefined label: v4l2-pix-fmt-x416 (if the link has no caption the label must precede a section header)
>> Documentation/output/videodev2.h.rst:6: WARNING: undefined label: v4l2-pix-fmt-x412m (if the link has no caption the label must precede a section header)
>> Documentation/output/videodev2.h.rst:6: WARNING: undefined label: v4l2-pix-fmt-x416m (if the link has no caption the label must precede a section header)
vim +6 Documentation/output/videodev2.h.rst
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-10-02 23:41 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=202310030701.UDDAgW9b-lkp@intel.com \
--to=lkp@intel.com \
--cc=git@amd.com \
--cc=hyun.kwon@xilinx.com \
--cc=linux-doc@vger.kernel.org \
--cc=monstr@monstr.eu \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=satish.nagireddy.nagireddy@xilinx.com \
/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).