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>,
Stephen Kitt <steve@sk2.org>,
Alexandru Tachici <alexandru.tachici@analog.com>
Subject: linux-next: build failure after merge of the hwmon-staging tree
Date: Mon, 24 Aug 2020 10:28:58 +1000 [thread overview]
Message-ID: <20200824102858.5554a2b2@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1637 bytes --]
Hi all,
After merging the hwmon-staging tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/hwmon/pmbus/adm1266.c: In function 'adm1266_probe':
drivers/hwmon/pmbus/adm1266.c:478:31: error: passing argument 2 of 'pmbus_do_probe' from incompatible pointer type [-Werror=incompatible-pointer-types]
478 | ret = pmbus_do_probe(client, id, &data->info);
| ^~
| |
| const struct i2c_device_id *
In file included from drivers/hwmon/pmbus/adm1266.c:20:
drivers/hwmon/pmbus/pmbus.h:492:73: note: expected 'struct pmbus_driver_info *' but argument is of type 'const struct i2c_device_id *'
492 | int pmbus_do_probe(struct i2c_client *client, struct pmbus_driver_info *info);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~
drivers/hwmon/pmbus/adm1266.c:478:8: error: too many arguments to function 'pmbus_do_probe'
478 | ret = pmbus_do_probe(client, id, &data->info);
| ^~~~~~~~~~~~~~
In file included from drivers/hwmon/pmbus/adm1266.c:20:
drivers/hwmon/pmbus/pmbus.h:492:5: note: declared here
492 | int pmbus_do_probe(struct i2c_client *client, struct pmbus_driver_info *info);
| ^~~~~~~~~~~~~~
cc1: some warnings being treated as errors
Caused by commit
9832ecffd8f8 ("hwmon: (pmbus) Add support for ADM1266")
interacting with commit
d46dc459db38 ("hwmon (pmbus) use simple i2c probe function")
I have used the hwmon-staging tree from next-20200821 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-08-24 0:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 0:28 Stephen Rothwell [this message]
2020-08-24 7:01 ` linux-next: build failure after merge of the hwmon-staging tree Guenter Roeck
-- strict thread matches above, loose matches on Subject: below --
2023-07-27 5:41 Stephen Rothwell
2023-01-24 22:24 Stephen Rothwell
2023-01-24 22:27 ` Guenter Roeck
2022-08-30 23:30 Stephen Rothwell
2022-08-31 12:03 ` Michael Shych
2022-05-10 12:26 Stephen Rothwell
2020-10-01 2:53 Stephen Rothwell
2020-10-01 15:09 ` Guenter Roeck
2020-04-28 6:36 Stephen Rothwell
2020-04-28 13:19 ` Guenter Roeck
2020-03-22 23:37 Stephen Rothwell
2020-03-22 23:45 ` Guenter Roeck
2019-02-25 23:55 Stephen Rothwell
2019-02-26 0:11 ` Guenter Roeck
2018-12-16 23:00 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=20200824102858.5554a2b2@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=alexandru.tachici@analog.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=steve@sk2.org \
/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).