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: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Grant Likely <grant.likely@linaro.org>,
	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 Linus' tree
Date: Mon, 29 Mar 2021 20:04:10 +1100	[thread overview]
Message-ID: <20210329200348.24a9a8be@canb.auug.org.au> (raw)

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

Hi all,

After merging Linus' tree, today's linux-next build (htmldocs) produced
these warnings:

include/linux/of.h:1211: warning: Function parameter or member 'output' not described in 'of_property_read_string_index'
include/linux/of.h:1211: warning: Excess function parameter 'out_string' description in 'of_property_read_string_index'

Introduced by commit

  a87fa1d81a9f ("of: Fix overflow bug in string property parsing functions")

include/linux/of.h:1480: warning: cannot understand function prototype: 'enum of_overlay_notify_action '

Introduced by commit

  39a842e22c1b ("of/overlay: add of overlay notifications")

I assume that these warnings have turned up now due to better(?) tooling.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2021-03-29  9:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29  9:04 Stephen Rothwell [this message]
2021-04-21  6:23 ` linux-next: build warnings after merge of Linus' tree Stephen Rothwell
2021-04-21 13:06   ` Rob Herring
2023-05-08  4:49 Stephen Rothwell
2023-05-08  4:52 ` Randy Dunlap
2023-05-08  4:53   ` Randy Dunlap
2023-05-08  7:50   ` Peter Zijlstra

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=20210329200348.24a9a8be@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=corbet@lwn.net \
    --cc=grant.likely@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mchehab+huawei@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.