From: Rob Herring <robherring2@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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: Re: linux-next: build warnings after merge of Linus' tree
Date: Wed, 21 Apr 2021 08:06:37 -0500 [thread overview]
Message-ID: <CAL_Jsq+0aPu75-mfQ+udkWWpJ3734J72V3fuXa_nzK9wfaX30Q@mail.gmail.com> (raw)
In-Reply-To: <20210421162320.1e3ff588@canb.auug.org.au>
On Wed, Apr 21, 2021 at 1:23 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> On Mon, 29 Mar 2021 20:04:10 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > 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")
> >
> > I assume that these warnings have turned up now due to better(?) tooling.
>
> I am still seeing these warnings (as of next-20210420).
A fix is now in my tree.
Rob
next prev parent reply other threads:[~2021-04-21 13:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 9:04 linux-next: build warnings after merge of Linus' tree Stephen Rothwell
2021-04-21 6:23 ` Stephen Rothwell
2021-04-21 13:06 ` Rob Herring [this message]
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=CAL_Jsq+0aPu75-mfQ+udkWWpJ3734J72V3fuXa_nzK9wfaX30Q@mail.gmail.com \
--to=robherring2@gmail.com \
--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=sfr@canb.auug.org.au \
/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).