All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Tony Luck <tony.luck@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the driver-core.current tree
Date: Thu, 21 Apr 2022 08:49:37 +0200	[thread overview]
Message-ID: <YmD+geU9CmjoVnN9@kroah.com> (raw)
In-Reply-To: <20220421152645.3a849198@canb.auug.org.au>

On Thu, Apr 21, 2022 at 03:26:45PM +1000, Stephen Rothwell wrote:
> 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.")

Tony, can you please send a fixup patch for this, or should I just
revert this commit for now?

thanks,

greg k-h

  reply	other threads:[~2022-04-21  6:51 UTC|newest]

Thread overview: 15+ 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 [this message]
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=YmD+geU9CmjoVnN9@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.