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: Mon, 31 Aug 2026 14:43:30 +0100 [thread overview]
Message-ID: <apWFAoNOz2pX5xiJ@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]
Hi all,
After merging the hwmon-staging tree, today's linux-next build
(arm64 defconfig) failed like this:
/tmp/next/build/drivers/hwmon/hwmon.c:344:13: error: redefinition of 'is_hwmon_device'
344 | static bool is_hwmon_device(struct device *dev)
| ^~~~~~~~~~~~~~~
/tmp/next/build/drivers/hwmon/hwmon.c:321:13: note: previous definition of 'is_hwmon_device' with type 'bool(struct device *)' {aka '_Bool(struct device *)'}
321 | static bool is_hwmon_device(struct device *dev)
| ^~~~~~~~~~~~~~~
/tmp/next/build/drivers/hwmon/hwmon.c:321:13: warning: 'is_hwmon_device' defined but not used [-Wunused-function]
Caused by commit
40b20f8e6b53e (hwmon: Ensure that 'dev' passed to hwmon_notify_event() is a hwmon device)
and the more intentional seeming
a40a97b27cd6b (hwmon: Ensure that 'dev' passed to hwmon_notify_event() is a hwmon device)
interacting, I assume some cherry pick issue or something. I have used
the tree from next-20260828 instead.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-08-31 13:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 13:43 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-10 11:45 linux-next: build failure after merge of the hwmon-staging tree Mark Brown
2026-06-10 12:58 ` Guenter Roeck
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-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=apWFAoNOz2pX5xiJ@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.