All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
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: Sat, 15 Jan 2022 12:33:38 +0100	[thread overview]
Message-ID: <668e68d07c114435f680eafd5444e1e3@walle.cc> (raw)
In-Reply-To: <20220115153212.593f534d@canb.auug.org.au>

Hi,

Am 2022-01-15 05:32, schrieb Stephen Rothwell:
> After merging the devicetree tree, today's linux-next build (htmldocs)
> produced these warnings:
> 
> include/linux/of.h:1037: warning: Function parameter or member 'np'
> not described in 'of_parse_phandle_with_optional_args'
> include/linux/of.h:1037: warning: Function parameter or member
> 'list_name' not described in 'of_parse_phandle_with_optional_args'
> include/linux/of.h:1037: warning: Function parameter or member
> 'cells_name' not described in 'of_parse_phandle_with_optional_args'
> include/linux/of.h:1037: warning: Function parameter or member 'index'
> not described in 'of_parse_phandle_with_optional_args'
> include/linux/of.h:1037: warning: Function parameter or member
> 'out_args' not described in 'of_parse_phandle_with_optional_args'
> 
> Introduced by commit
> 
>   952c4865d27a ("of: base: add of_parse_phandle_with_optional_args()")

Sorry about that, just sent a fixes patch:
https://lore.kernel.org/linux-devicetree/20220115113156.435037-1-michael@walle.cc/

-michael

  reply	other threads:[~2022-01-15 11:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-15  4:32 linux-next: build warnings after merge of the devicetree tree Stephen Rothwell
2022-01-15 11:33 ` Michael Walle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-03-29  8:53 Stephen Rothwell
2021-03-29  9:48 ` Lee Jones
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=668e68d07c114435f680eafd5444e1e3@walle.cc \
    --to=michael@walle.cc \
    --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 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.