From: Mark Brown <broonie@kernel.org>
To: Mike Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Peng Fan <peng.fan@nxp.com>,
Brian Masney <bmasney@redhat.com>
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 clk tree
Date: Mon, 17 Aug 2026 16:31:11 +0100 [thread overview]
Message-ID: <aoMpP0R8qSzhuEId@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 566 bytes --]
Hi all,
After merging the clk tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
ERROR: modpost: drivers/clk/clk-scmi-oem.ko: missing MODULE_LICENSE()
WARNING: modpost: drivers/clk/clk-scmi-oem.ko: missing MODULE_DESCRIPTION()
ERROR: modpost: drivers/clk/clk-scmi.ko: symbol 'scmi_clk_oem_init' undefined!
ERROR: modpost: drivers/clk/clk-scmi-oem.ko: symbol 'scmi_proto_clk_ops' undefined!
Caused by commit
77369b1e6a371 (clk: scmi: Add i.MX95 OEM extension support for SCMI clock driver)
I have used the tree from next-20260814 instead.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-08-17 15:31 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 15:31 Mark Brown [this message]
2026-08-18 0:57 ` linux-next: build failure after merge of the clk tree Peng Fan (OSS)
-- strict thread matches above, loose matches on Subject: below --
2024-07-16 0:41 Stephen Rothwell
2024-07-16 18:26 ` Stephen Boyd
2024-01-03 23:04 Stephen Rothwell
2024-01-04 0:59 ` Stephen Boyd
2023-04-02 23:59 Stephen Rothwell
2023-04-05 0:28 ` Stephen Rothwell
2020-05-11 0:55 Stephen Rothwell
2020-05-13 3:20 ` Stephen Boyd
2020-05-13 3:28 ` Stephen Boyd
2020-01-07 21:47 Stephen Rothwell
2019-07-02 0:01 Stephen Rothwell
2019-07-02 1:14 ` Stephen Rothwell
2019-07-02 2:03 ` Stephen Rothwell
2019-07-05 1:24 ` Stephen Rothwell
2019-07-12 17:53 ` Stephen Boyd
2019-05-02 23:25 Stephen Rothwell
2019-05-03 15:55 ` Stephen Boyd
2018-11-29 22:03 Stephen Rothwell
2018-01-01 21:51 Stephen Rothwell
2018-01-02 19:58 ` Stephen Boyd
2017-12-10 23:16 Stephen Rothwell
2017-12-14 0:57 ` Stephen Boyd
2017-06-05 0:14 Stephen Rothwell
2015-08-12 7:19 Stephen Rothwell
2015-08-12 7:45 ` Geert Uytterhoeven
2015-08-12 8:23 ` Stephen Boyd
2015-08-12 8:03 ` Stephen Boyd
2015-07-27 4:11 Stephen Rothwell
2015-08-03 10:08 ` Tony Lindgren
2015-08-07 23:56 ` Stephen Boyd
2015-08-13 11:04 ` Olof Johansson
2015-02-27 3:08 Stephen Rothwell
2015-02-27 17:42 ` Stephen Boyd
2015-03-04 9:56 ` Geert Uytterhoeven
2015-03-05 0:15 ` Mike Turquette
2015-02-26 2:14 Stephen Rothwell
2015-02-26 9:09 ` Krzysztof Kozlowski
2015-02-27 0:01 ` Mike Turquette
2015-02-27 0:06 ` Stephen Rothwell
2014-12-16 3:45 Stephen Rothwell
[not found] ` <20141216072034.29014.12434@quantum>
2014-12-17 3:47 ` Stephen Rothwell
2014-01-29 3:32 Stephen Rothwell
2014-01-29 10:02 ` Sebastian Hesselbarth
2013-04-15 5:04 Stephen Rothwell
2013-04-15 7:03 ` Sebastian Hesselbarth
2013-04-16 0:42 ` Mike Turquette
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=aoMpP0R8qSzhuEId@sirena.org.uk \
--to=broonie@kernel.org \
--cc=bmasney@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=sboyd@kernel.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