All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the hwmon-staging tree
Date: Tue, 3 Dec 2024 19:33:17 +0000	[thread overview]
Message-ID: <Z09c_U2l8SqLQG-n@sirena.org.uk> (raw)

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

Hi all,

After merging the hwmon-staging tree, today's linux-next build
(x86 allmodconfig) failed like this:

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.

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

             reply	other threads:[~2024-12-03 19:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03 19:33 Mark Brown [this message]
2024-12-03 19:40 ` linux-next: build failure after merge of the hwmon-staging tree Mark Brown
2024-12-03 19:53   ` Guenter Roeck
2024-12-03 20:02     ` Mark Brown
2024-12-03 19:52 ` Guenter Roeck
  -- strict thread matches above, loose matches on Subject: below --
2026-08-31 13:43 Mark Brown
2026-06-10 11:45 Mark Brown
2026-06-10 12:58 ` 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-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=Z09c_U2l8SqLQG-n@sirena.org.uk \
    --to=broonie@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.