From: Guenter Roeck <linux@roeck-us•net>
To: Mark Brown <broonie@kernel•org>, Andi Shyti <andi.shyti@kernel•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build failure after merge of the hwmon-staging tree
Date: Tue, 3 Dec 2024 11:53:58 -0800 [thread overview]
Message-ID: <d57e049a-9d1b-4229-84ba-0933cc0315d4@roeck-us.net> (raw)
In-Reply-To: <cba440fc-88c6-444c-af57-046ebedd60c2@sirena.org.uk>
On 12/3/24 11:40, Mark Brown wrote:
> On Tue, Dec 03, 2024 at 07:33:22PM +0000, Mark Brown wrote:
>> Hi all,
>>
>> After merging the hwmon-staging tree, today's linux-next build
>> (x86 allmodconfig) failed like this:
>
> Sorry, this was the i2c-host tree rather than the hwmon-staging tree.
>
I think it is (or should be) the hwmon-next tree.
Guenter
>>
>> In file included from /tmp/next/build/include/linux/module.h:22,
>> from /tmp/next/build/include/linux/device/driver.h:21,
>> from /tmp/next/build/include/linux/device.h:32,
>> from /tmp/next/build/include/linux/hwmon-sysfs.h:10,
>> from /tmp/next/build/drivers/hwmon/pmbus/tps25990.c:9:
>> /tmp/next/build/drivers/hwmon/pmbus/tps25990.c:437:18: error: expected ',' or ';' before 'PMBUS'
>> 437 | MODULE_IMPORT_NS(PMBUS);
>> | ^~~~~
>> /tmp/next/build/include/linux/moduleparam.h:26:61: note: in definition of macro '__MODULE_INFO'
>> 26 | = __MODULE_INFO_PREFIX __stringify(tag) "=" info
>> | ^~~~
>> /tmp/next/build/include/linux/module.h:299:33: note: in expansion of macro 'MODULE_INFO'
>> 299 | #define MODULE_IMPORT_NS(ns) MODULE_INFO(import_ns, ns)
>> | ^~~~~~~~~~~
>> /tmp/next/build/drivers/hwmon/pmbus/tps25990.c:437:1: note: in expansion of macro 'MODULE_IMPORT_NS'
>> 437 | MODULE_IMPORT_NS(PMBUS);
>> | ^~~~~~~~~~~~~~~~
>>
>> Caused by an interaction with Linus' tree. I have used the hwmon tree
>> from 20241128 instead.
>
>
next prev parent reply other threads:[~2024-12-03 19:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 19:33 linux-next: build failure after merge of the hwmon-staging tree Mark Brown
2024-12-03 19:40 ` Mark Brown
2024-12-03 19:53 ` Guenter Roeck [this message]
2024-12-03 20:02 ` Mark Brown
2024-12-03 19:52 ` 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-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=d57e049a-9d1b-4229-84ba-0933cc0315d4@roeck-us.net \
--to=linux@roeck-us$(echo .)net \
--cc=andi.shyti@kernel$(echo .)org \
--cc=broonie@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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