From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Krzysztof Adamski <krzysztof.adamski@nokia.com>,
Alexander Sverdlin <alexander.sverdlin@nokia.com>
Subject: linux-next: build warning after merge of the hwmon-staging tree
Date: Thu, 6 Jun 2019 10:34:30 +1000 [thread overview]
Message-ID: <20190606103430.74fd20f2@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 502 bytes --]
Hi all,
After merging the hwmon-staging tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/hwmon/pmbus/adm1275.c: In function 'adm1275_write_pmon_config':
drivers/hwmon/pmbus/adm1275.c:179:23: warning: unused variable 'data' [-Wunused-variable]
struct adm1275_data *data = to_adm1275_data(info);
^~~~
Introduced by commit
438318513375 ("hwmon: (pmbus/adm1275) support PMBUS_VIRT_*_SAMPLES")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-06-06 0:34 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 0:34 Stephen Rothwell [this message]
2019-07-01 2:26 linux-next: build warning after merge of the hwmon-staging tree Stephen Rothwell
2020-02-10 22:23 Stephen Rothwell
2020-02-11 0:24 ` Guenter Roeck
2020-11-30 0:56 Stephen Rothwell
2020-11-30 1:14 ` Paul Barker
2020-11-30 14:53 ` Guenter Roeck
2020-12-07 7:51 Stephen Rothwell
2021-01-29 7:03 Stephen Rothwell
2021-03-12 3:50 Stephen Rothwell
2021-03-12 4:00 ` Chris Packham
2021-03-12 4:45 ` Stephen Rothwell
2021-03-30 7:27 Stephen Rothwell
2021-03-30 10:38 ` Guenter Roeck
2021-03-30 20:25 ` Chris Packham
2021-03-30 20:55 ` Guenter Roeck
2021-06-10 0:21 Stephen Rothwell
2021-06-10 3:38 ` Guenter Roeck
2021-12-20 0:00 Stephen Rothwell
2021-12-20 11:31 Stephen Rothwell
2022-02-04 5:16 Stephen Rothwell
2022-02-04 5:25 ` Guenter Roeck
2022-02-10 7:51 Stephen Rothwell
2022-02-10 8:50 ` Lee Jones
2022-02-10 17:33 ` Guenter Roeck
2022-02-10 18:07 ` Lee Jones
2022-02-10 18:22 ` Guenter Roeck
2022-05-03 7:22 Stephen Rothwell
2022-05-03 7:34 ` Michael Walle
2022-05-03 13:08 ` Guenter Roeck
2022-05-10 10:11 Stephen Rothwell
2022-05-10 10:47 ` Zev Weiss
2022-05-10 14:03 ` Guenter Roeck
2022-08-31 5:30 Stephen Rothwell
2023-10-30 5:15 Stephen Rothwell
2023-12-12 3:12 Stephen Rothwell
2023-12-12 5:11 ` Guenter Roeck
2024-03-26 5:03 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=20190606103430.74fd20f2@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=alexander.sverdlin@nokia.com \
--cc=krzysztof.adamski@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
/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).