linux-kernel - Re: linux-next: build warning after merge of the pinctrl tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 27 Oct 2021 12:10:45 +0100
From:   Marc Zyngier <maz@...nel.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linus Walleij <linus.walleij@...aro.org>,
        Mauro Carvalho Chehab <mchehab@...nel.org>,
        Jonathan Corbet <corbet@....net>,
        Joey Gouly <joey.gouly@....com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warning after merge of the pinctrl tree

On Wed, 27 Oct 2021 12:01:18 +0100,
Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> 
> Hi all,
> 
> After merging the pinctrl tree, today's linux-next build (htmldocs)
> produced this warning:
> 
> include/linux/gpio/driver.h:284: warning: Function parameter or member 'parent_handler_data_array' not described in 'gpio_irq_chip'
> 
> Introduced by commit
> 
>   cfe6807d82e9 ("gpio: Allow per-parent interrupt data")
> 
> But may actually be a problem with the tool :-(

I guess the tool doesn't like having two fields that are part of a
union documented together... Happy to tweak it if someone tells me how
this should be written.

	M.

-- 
Without deviation from the norm, progress is not possible.