netdev - Re: linux-next: build warning after merge of the net-next 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <2b553780-f0a8-f9d7-4401-65762952fbdd@infradead.org>
Date:   Fri, 29 Oct 2021 19:10:02 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     "Russell King (Oracle)" <linux@...linux.org.uk>,
        Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     David Miller <davem@...emloft.net>,
        Networking <netdev@...r.kernel.org>,
        Mauro Carvalho Chehab <mchehab@...nel.org>,
        Jonathan Corbet <corbet@....net>,
        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 net-next tree

On 10/27/21 4:34 AM, Russell King (Oracle) wrote:
> On Wed, Oct 27, 2021 at 10:07:21PM +1100, Stephen Rothwell wrote:
>> Hi all,
>>
>> After merging the net-next tree, today's linux-next build (htmldocs)
>> produced this warning:
>>
>> include/linux/phylink.h:82: warning: Function parameter or member 'DECLARE_PHY_INTERFACE_MASK(supported_interfaces' not described in 'phylink_config'
>>
>> Introduced by commit
>>
>>    38c310eb46f5 ("net: phylink: add MAC phy_interface_t bitmap")
>>
>> Or maybe this is a problem with the tool ...
> 
> Hmm. Looks like it is a tooling problem.
> 
>   * @supported_interfaces: bitmap describing which PHY_INTERFACE_MODE_xxx
>   *                        are supported by the MAC/PCS.
> 
>          DECLARE_PHY_INTERFACE_MASK(supported_interfaces);
> 
> I'm guessing the tool doesn't use the preprocessed source. I'm not sure
> what the solution to this would be.
> 

I just sent a patch to scripts/kernel-doc to support that macro.

-- 
~Randy