public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: MyungJoo Ham <myungjoo.ham@samsung.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Leonard Crestez <leonard.crestez@nxp.com>
Subject: linux-next: build warning after merge of the devfreq tree
Date: Mon, 26 Aug 2019 21:50:17 +1000	[thread overview]
Message-ID: <20190826215017.02ab0d34@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 487 bytes --]

Hi all,

After merging the devfreq tree, today's linux-next build (x86_64
allmodconfig) produced this warning:

drivers/devfreq/governor_passive.c: In function 'devfreq_passive_event_handler':
drivers/devfreq/governor_passive.c:152:17: warning: unused variable 'dev' [-Wunused-variable]
  struct device *dev = devfreq->dev.parent;
                 ^~~

Introduced by commit

  0ef7c7cce43f ("PM / devfreq: passive: Use non-devm notifiers")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2019-08-26 11:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-26 11:50 Stephen Rothwell [this message]
2019-08-26 12:37 ` linux-next: build warning after merge of the devfreq tree Leonard Crestez
2019-08-26 12:43 ` [PATCH] PM / devfreq: passive: fix compiler warning MyungJoo Ham
2019-08-26 12:46 ` linux-next: build warning after merge of the devfreq tree MyungJoo Ham
2019-08-28  9:06   ` Rafael J. Wysocki

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=20190826215017.02ab0d34@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=leonard.crestez@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=myungjoo.ham@samsung.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