From: "Luck, Tony" <tony.luck@intel•com>
To: Greg KH <gregkh@linuxfoundation•org>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: [PATCH v2] topology/sysfs: Fix allnoconfig build breakage.
Date: Thu, 21 Apr 2022 09:19:59 -0700 [thread overview]
Message-ID: <YmGEL2klp4S97UiH@agluck-desk3.sc.intel.com> (raw)
In-Reply-To: <YmF+FTxgu2U4/oPA@kroah.com>
drivers/base/topology.c: In function 'topology_is_visible':
drivers/base/topology.c:158:24: warning: unused variable 'dev' [-Wunused-variable]
158 | struct device *dev = kobj_to_dev(kobj);
This is because the topology_ppin(dev->id) macro expands to:
(cpu_data(dev->id).ppin)
and with CONFIG_SMP=n the cpu_data() macro expands to boot_cpu_data
(ignoring its argument) with the end result:
boot_cpu_data.ppin
Fix by just checking whether the boot_cpu has a PPIN instead of whether
this specific CPU has one.
Fixes: c3702a746ff5 ("topology/sysfs: Hide PPIN on systems that do not support it.")
Reported-by: Stephen Rothwell <sfr@canb•auug.org.au>
Signed-off-by: Tony Luck <tony.luck@intel•com>
---
I don't believe it will ever be possible to have no PPIN on the boot CPU,
but somehow have PPINs on other CPUs (or vice versa)
drivers/base/topology.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/base/topology.c b/drivers/base/topology.c
index 706dbf8bf249..11a56a10188d 100644
--- a/drivers/base/topology.c
+++ b/drivers/base/topology.c
@@ -155,9 +155,7 @@ static struct attribute *default_attrs[] = {
static umode_t topology_is_visible(struct kobject *kobj,
struct attribute *attr, int unused)
{
- struct device *dev = kobj_to_dev(kobj);
-
- if (attr == &dev_attr_ppin.attr && !topology_ppin(dev->id))
+ if (attr == &dev_attr_ppin.attr && !boot_cpu_data.ppin)
return 0;
return attr->mode;
--
2.35.1
next prev parent reply other threads:[~2022-04-21 16:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 5:26 linux-next: build warning after merge of the driver-core.current tree Stephen Rothwell
2022-04-21 6:49 ` Greg KH
2022-04-21 15:45 ` [PATCH] topology/sysfs: Fix allnoconfig build breakage Luck, Tony
2022-04-21 15:53 ` Greg KH
2022-04-21 16:19 ` Luck, Tony [this message]
2022-04-21 23:22 ` [PATCH v2] " Stephen Rothwell
2022-04-21 23:38 ` Luck, Tony
2022-04-22 0:00 ` Stephen Rothwell
2022-04-22 2:51 ` Luck, Tony
2022-04-22 6:00 ` Greg KH
2022-04-22 6:27 ` Greg KH
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=YmGEL2klp4S97UiH@agluck-desk3.sc.intel.com \
--to=tony.luck@intel$(echo .)com \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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