From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg KH <greg@kroah.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Tony Luck <tony.luck@intel.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 driver-core.current tree
Date: Thu, 21 Apr 2022 15:26:45 +1000 [thread overview]
Message-ID: <20220421152645.3a849198@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 507 bytes --]
Hi all,
After merging the driver-core.current tree, today's linux-next build
(x86_64 allnoconfig) produced this warning:
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);
| ^~~
Introduced by commit
aa63a74d4535 ("topology/sysfs: Hide PPIN on systems that do not support it.")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-04-21 5:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 5:26 Stephen Rothwell [this message]
2022-04-21 6:49 ` linux-next: build warning after merge of the driver-core.current tree 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 ` [PATCH v2] " Luck, Tony
2022-04-21 23:22 ` 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
-- strict thread matches above, loose matches on Subject: below --
2010-04-29 23:35 linux-next: build warning after merge of the driver-core.current tree Stephen Rothwell
2010-04-29 23:43 ` Greg KH
2010-04-29 23:45 ` Greg KH
2010-04-30 0:01 ` Stephen Rothwell
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=20220421152645.3a849198@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=greg@kroah.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=tony.luck@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).