linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
	Zhang Rui <rui.zhang@intel.com>
Cc: Bernard Zhao <bernard@vivo.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 thermal tree
Date: Tue, 27 Oct 2020 11:34:37 +1100	[thread overview]
Message-ID: <20201027113437.76d3fe13@canb.auug.org.au> (raw)

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

Hi all,

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

drivers/thermal/gov_power_allocator.c: In function 'power_allocator_unbind':
drivers/thermal/gov_power_allocator.c:587:33: warning: unused variable 'params' [-Wunused-variable]
  587 |  struct power_allocator_params *params = tz->governor_data;
      |                                 ^~~~~~

Introduced by commit

  ee7e92c62370 ("drivers/thermal: Remove unnecessary structure members allocated_tzp")

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2020-10-27  0:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-27  0:34 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-03-02 23:42 linux-next: build warning after merge of the thermal tree Stephen Rothwell
2020-03-03  0:17 ` Daniel Lezcano
2019-10-21 23:23 Stephen Rothwell
2019-10-22  9:50 ` Amit Kucheria
2019-10-22 11:18   ` Stephen Rothwell
2019-10-24  7:26     ` Amit Kucheria
2019-10-29  9:05 ` Geert Uytterhoeven
2019-04-30  3:48 Stephen Rothwell
2017-09-01  0:52 Stephen Rothwell
2016-08-24  3:38 Stephen Rothwell
2016-08-24  7:56 ` Zhang Rui

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=20201027113437.76d3fe13@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=bernard@vivo.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rui.zhang@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).