From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mauro Carvalho Chehab <mchehab@kernel•org>
Cc: Sakari Ailus <sakari.ailus@linux•intel.com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build warning after merge of the v4l-dvb-next tree
Date: Fri, 2 Feb 2024 14:54:12 +1100 [thread overview]
Message-ID: <20240202145412.336db5b2@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 516 bytes --]
Hi all,
After merging the v4l-dvb-next tree, today's linux-next build (htmldocs)
produced this warning:
Documentation/driver-api/media/v4l2-common:6: include/media/v4l2-common.h:566: ERROR: Unexpected indentation.
Documentation/driver-api/media/v4l2-common:6: include/media/v4l2-common.h:567: WARNING: Block quote ends without a blank line; unexpected unindent.
Introduced by commit
a68e88e2cf9e ("media: v4l: Add a helper for setting up link-frequencies control")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-02-02 3:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 3:54 Stephen Rothwell [this message]
2024-02-02 6:40 ` [PATCH 1/1] media: v4l: Fix link frequency helper's kernel-doc Sakari Ailus
2024-02-02 13:30 ` Mauro Carvalho Chehab
2024-02-02 13:41 ` Sakari Ailus
-- strict thread matches above, loose matches on Subject: below --
2023-05-15 4:01 linux-next: build warning after merge of the v4l-dvb-next tree Stephen Rothwell
2022-11-09 5:20 Stephen Rothwell
2022-11-09 14:50 ` Benjamin MUGNIER
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=20240202145412.336db5b2@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mchehab@kernel$(echo .)org \
--cc=sakari.ailus@linux$(echo .)intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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