All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Rob Herring <robherring2@gmail.com>
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: Re: linux-next: build warning after merge of the overlayfs tree
Date: Wed, 21 Apr 2021 16:26:22 +1000	[thread overview]
Message-ID: <20210421162622.0c686883@canb.auug.org.au> (raw)
In-Reply-To: <20210329201426.78d4b28b@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 669 bytes --]

Hi all,

On Mon, 29 Mar 2021 20:14:26 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> 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")

I am still seeing this warning (as of next-20210420).
-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2021-04-21  6:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29  9:14 linux-next: build warning after merge of the overlayfs tree Stephen Rothwell
2021-03-29  9:28 ` Miklos Szeredi
2021-03-31  0:16   ` Stephen Rothwell
2021-04-21  6:26 ` Stephen Rothwell [this message]
  -- 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=20210421162622.0c686883@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=robh@kernel.org \
    --cc=robherring2@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.