From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Helen Koike <helen.koike@collabora.com>,
Jacob Chen <jacob2.chen@rock-chips.com>,
Shunqian Zheng <zhengsq@rock-chips.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warnings after merge of the v4l-dvb tree
Date: Wed, 18 Nov 2020 16:32:29 +1100 [thread overview]
Message-ID: <20201118163229.1cda4547@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 581 bytes --]
Hi all,
After merging the v4l-dvb tree, today's linux-next build (htmldocs)
produced these warnings:
Documentation/output/videodev2.h.rst:6: WARNING: undefined label: v4l2-meta-fmt-rk-isp1-params (if the link has no caption the label must precede a section header)
Documentation/output/videodev2.h.rst:6: WARNING: undefined label: v4l2-meta-fmt-rk-isp1-stat-3a (if the link has no caption the label must precede a section header)
Introduced by commit
df22026aebd8 ("media: videodev2.h, v4l2-ioctl: add rkisp1 meta buffer format")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-11-18 5:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 5:32 Stephen Rothwell [this message]
2020-11-18 14:26 ` linux-next: build warnings after merge of the v4l-dvb tree Helen Koike
-- strict thread matches above, loose matches on Subject: below --
2021-03-04 1:50 Stephen Rothwell
2021-03-04 15:12 ` Mauro Carvalho Chehab
2011-03-17 0:33 Stephen Rothwell
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=20201118163229.1cda4547@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=helen.koike@collabora.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jacob2.chen@rock-chips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=zhengsq@rock-chips.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).