linux-kernel - Re: linux-next: build warning after merge of the spi 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] [thread-next>] [day] [month] [year] [list]

Date: Thu, 8 Feb 2024 14:32:15 +0100
From: Amadeusz Sławiński
 <amadeuszx.slawinski@...ux.intel.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>, Mark Brown <broonie@...nel.org>
Cc: Cezary Rojewski <cezary.rojewski@...el.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 spi tree

On 2/8/2024 4:52 AM, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the spi tree, today's linux-next build (htmldocs) produced
> this warning:
> 
> Warning: /sys/devices/pci0000:00/<dev>/fw_version is defined 2 times:  Documentation/ABI/testing/sysfs-bus-pci-devices-avs:0  Documentation/ABI/testing/sysfs-bus-pci-devices-catpt:0
> 
> Introduced by commit
> 
>    148b93a5062d ("ASoC: Intel: avs: Expose FW version with sysfs")
> 
> You need to make the "<dev>" part unique.
> 

Ah! The avs path should've been:
/sys/devices/pci0000:00/<dev>/avs/fw_version
Will "avs/" in path this fix the error?
As far as I know there are at least two possible devices, that's why we 
used <dev> in path.