linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	James Clark <james.clark@arm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the char-misc.current tree
Date: Mon, 24 Oct 2022 08:34:38 +0200	[thread overview]
Message-ID: <Y1Yx/ioaPRA9YIzM@kroah.com> (raw)
In-Reply-To: <20221024135752.2b83af97@canb.auug.org.au>

On Mon, Oct 24, 2022 at 01:57:52PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the char-misc.current tree, today's linux-next build
> (arm64 defconfig) produced these warnings:
> 
> drivers/hwtracing/coresight/coresight-cti-core.c: In functio
> n 'cti_enable_hw':
> drivers/hwtracing/coresight/coresight-cti-core.c:93:24: warning: unused variable 'dev' [-Wunused-variable]
>    93 |         struct device *dev = &drvdata->csdev->dev;
>       |                        ^~~
> drivers/hwtracing/coresight/coresight-cti-core.c: In function 'cti_disable_hw':
> drivers/hwtracing/coresight/coresight-cti-core.c:154:24: warning: unused variable 'dev' [-Wunused-variable]
>   154 |         struct device *dev = &drvdata->csdev->dev;
>       |                        ^~~
> 
> Introduced by commit
> 
>   665c157e0204 ("coresight: cti: Fix hang in cti_disable_hw()")

Thanks for the report, I have now reverted this in my tree.

greg k-h

  reply	other threads:[~2022-10-24  6:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24  2:57 linux-next: build warnings after merge of the char-misc.current tree Stephen Rothwell
2022-10-24  6:34 ` Greg KH [this message]
2022-10-24  9:45   ` Suzuki K Poulose

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=Y1Yx/ioaPRA9YIzM@kroah.com \
    --to=greg@kroah.com \
    --cc=arnd@arndb.de \
    --cc=james.clark@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=suzuki.poulose@arm.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).