From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Frank Rowand <frank.rowand@sony.com>,
Rob Herring <robh@kernel.org>,
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 overlayfs tree
Date: Mon, 29 Mar 2021 20:14:26 +1100 [thread overview]
Message-ID: <20210329201426.78d4b28b@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 504 bytes --]
Hi all,
After merging the overlayfs tree, today's linux-next build (htmldocs)
produced this warning:
Documentation/devicetree/kernel-api:56: /home/sfr/next/next/drivers/of/overlay.c:1184: WARNING: Inline emphasis start-string without end-string.
Introduced by commit
24789c5ce5a3 ("of: overlay: detect cases where device tree may become corrupt")
Probably exposed by commit
8c8239c2c1fb ("of: Add missing 'Return' section in kerneldoc comments")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-03-29 9:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 9:14 Stephen Rothwell [this message]
2021-03-29 9:28 ` linux-next: build warning after merge of the overlayfs tree Miklos Szeredi
2021-03-31 0:16 ` Stephen Rothwell
2021-04-21 6:26 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2021-07-20 6:38 Stephen Rothwell
2021-07-21 13:39 ` Miklos Szeredi
2017-11-08 22:33 Stephen Rothwell
2017-11-09 3:59 ` Chandan Rajendra
2017-05-17 0:19 Stephen Rothwell
2017-05-17 5:00 ` Amir Goldstein
2016-11-22 0:19 Stephen Rothwell
2016-11-22 8:41 ` Miklos Szeredi
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=20210329201426.78d4b28b@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=frank.rowand@sony.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).