From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Vadim Pasternak <vadimp@nvidia.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the hwmon-staging tree
Date: Thu, 1 Oct 2020 08:09:44 -0700 [thread overview]
Message-ID: <20201001150944.GA64648@roeck-us.net> (raw)
In-Reply-To: <20201001125310.3399978a@canb.auug.org.au>
On Thu, Oct 01, 2020 at 12:53:10PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the hwmon-staging tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/hwmon/pmbus/mp2975.c: In function 'mp2975_probe':
> drivers/hwmon/pmbus/mp2975.c:740:32: error: passing argument 2 of 'pmbus_do_probe' from incompatible pointer type [-Werror=incompatible-pointer-types]
> 740 | return pmbus_do_probe(client, id, info);
> | ^~
> | |
> | const struct i2c_device_id *
> In file included from drivers/hwmon/pmbus/mp2975.c:13:
> 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/mp2975.c:740:9: error: too many arguments to function 'pmbus_do_probe'
> 740 | return pmbus_do_probe(client, id, info);
> | ^~~~~~~~~~~~~~
> In file included from drivers/hwmon/pmbus/mp2975.c:13:
> drivers/hwmon/pmbus/pmbus.h:492:5: note: declared here
> 492 | int pmbus_do_probe(struct i2c_client *client, struct pmbus_driver_info *info);
> | ^~~~~~~~~~~~~~
>
> Caused by commit
>
> dd38ac315b23 ("hwmon: (pmbus) Add support for MPS Multi-phase mp2975 controller")
>
Oops, sorry, got caught in API changes. Fixed.
Guenter
> I have used the hwmon-staging tree from next-20200930 for today.
>
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2020-10-01 15:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 2:53 linux-next: build failure after merge of the hwmon-staging tree Stephen Rothwell
2020-10-01 15:09 ` Guenter Roeck [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-03 19:33 Mark Brown
2024-12-03 19:40 ` Mark Brown
2024-12-03 19:53 ` Guenter Roeck
2024-12-03 20:02 ` Mark Brown
2024-12-03 19:52 ` Guenter Roeck
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-08-24 0:28 Stephen Rothwell
2020-08-24 7:01 ` 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=20201001150944.GA64648@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=vadimp@nvidia.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