From: Lee Jones <lee.jones@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Rob Herring <robherring2@gmail.com>,
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 the devicetree tree
Date: Mon, 29 Mar 2021 10:48:47 +0100 [thread overview]
Message-ID: <20210329094847.GD2916463@dell> (raw)
In-Reply-To: <20210329195351.3322aee1@canb.auug.org.au>
On Mon, 29 Mar 2021, Stephen Rothwell wrote:
> Hi all,
>
> After merging the devicetree tree, today's linux-next build (htmldocs)
> produced these warnings:
>
> drivers/of/base.c:1781: warning: Excess function parameter 'prob' description in '__of_add_property'
> drivers/of/base.c:1804: warning: Excess function parameter 'prob' description in 'of_add_property'
> drivers/of/base.c:1855: warning: Function parameter or member 'prop' not described in 'of_remove_property'
> drivers/of/base.c:1855: warning: Excess function parameter 'prob' description in 'of_remove_property'
>
> Introduced by commit
>
> 3637d49e1121 ("of: base: Fix some formatting issues and provide missing descriptions")
Ah, I see. Will fix. Please bear with me.
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2021-03-29 9:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 8:53 linux-next: build warnings after merge of the devicetree tree Stephen Rothwell
2021-03-29 9:48 ` Lee Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-15 4:32 Stephen Rothwell
2022-01-15 11:33 ` Michael Walle
2020-03-16 1:11 Stephen Rothwell
2018-09-20 1:47 Stephen Rothwell
2018-09-20 13:49 ` Rob Herring
2018-09-05 0:39 Stephen Rothwell
2018-09-05 1:54 ` Stephen Rothwell
2018-09-05 11:20 ` Rob Herring
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=20210329094847.GD2916463@dell \
--to=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=robherring2@gmail.com \
--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).