From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "Bjorn Helgaas" <bhelgaas@google•com>,
"Lorenzo Pieralisi" <lpieralisi@kernel•org>,
"Krzysztof Wilczyński" <kwilczynski@kernel•org>
Cc: Mario Limonciello <mario.limonciello@amd•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build warning after merge of the pci tree
Date: Fri, 18 Jul 2025 22:41:18 +1000 [thread overview]
Message-ID: <20250718224118.5b3f22b0@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 795 bytes --]
Hi all,
After merging the pci tree, today's linux-next build (sparc defconfig)
produced this warning:
In file included from /home/sfr/next/next/include/linux/pci.h:37,
from /home/sfr/next/next/drivers/pci/pci-sysfs.c:19:
/home/sfr/next/next/include/linux/device.h:199:33: warning: 'dev_attr_boot_display' defined but not used [-Wunused-variable]
199 | struct device_attribute dev_attr_##_name = __ATTR_RO(_name)
| ^~~~~~~~~
/home/sfr/next/next/drivers/pci/pci-sysfs.c:688:8: note: in expansion of macro 'DEVICE_ATTR_RO'
688 | static DEVICE_ATTR_RO(boot_display);
| ^~~~~~~~~~~~~~
Introduced by commit
c4f2dc1e5293 ("PCI: Add a new 'boot_display' attribute")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-07-18 12:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 12:41 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-21 10:26 linux-next: build warning after merge of the pci tree Stephen Rothwell
2025-05-21 12:10 ` Krzysztof Wilczyński
2025-03-03 7:26 Stephen Rothwell
2025-03-03 7:50 ` Krzysztof Wilczyński
2025-03-03 9:46 ` Krzysztof Wilczyński
2024-07-01 9:24 Stephen Rothwell
2024-07-01 19:37 ` Bjorn Helgaas
2024-07-01 20:15 ` Krzysztof Wilczyński
2024-07-02 6:59 ` Philipp Stanner
2020-09-09 2:38 Stephen Rothwell
2020-09-15 3:43 ` Stephen Rothwell
2020-09-09 2:37 Stephen Rothwell
2020-09-09 16:06 ` Rob Herring
2020-09-15 3:47 ` Stephen Rothwell
2020-09-15 10:53 ` Lorenzo Pieralisi
2020-09-15 17:22 ` Bjorn Helgaas
2020-09-02 1:07 Stephen Rothwell
2020-09-02 12:33 ` Bjorn Helgaas
2020-09-02 14:13 ` Vaibhav Gupta
2020-08-05 1:32 Stephen Rothwell
2020-08-05 2:29 ` Bjorn Helgaas
2016-06-23 1:51 Stephen Rothwell
2016-06-23 16:48 ` Bjorn Helgaas
2016-06-24 8:07 ` Johannes Thumshirn
2013-09-03 23:55 Stephen Rothwell
2013-09-03 23:59 ` Bjorn Helgaas
2012-12-10 9:03 Stephen Rothwell
2012-12-10 21:25 ` Bjorn Helgaas
2012-12-10 23:21 ` Bjorn Helgaas
2012-05-01 6:08 Stephen Rothwell
2012-05-01 7:35 ` Yinghai Lu
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=20250718224118.5b3f22b0@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=bhelgaas@google$(echo .)com \
--cc=kwilczynski@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=lpieralisi@kernel$(echo .)org \
--cc=mario.limonciello@amd$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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