From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Peng Fan <peng.fan@nxp.com>,
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 scmi tree
Date: Wed, 28 Aug 2024 10:15:31 +1000 [thread overview]
Message-ID: <20240828101531.38e633d8@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 500 bytes --]
Hi all,
After merging the scmi tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: modpost: missing MODULE_LICENSE() in drivers/firmware/arm_scmi/vendors/imx/imx-sm-bbm.o
ERROR: modpost: missing MODULE_LICENSE() in drivers/firmware/arm_scmi/vendors/imx/imx-sm-misc.o
Caused by commit
00bdb213e944 ("firmware: arm_scmi: add initial support for i.MX MISC protocol")
I have used the scmi tree from next-20240827 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-08-28 0:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 0:15 Stephen Rothwell [this message]
2024-08-28 5:29 ` linux-next: build failure after merge of the scmi tree Peng Fan
2024-08-28 8:48 ` Sudeep Holla
-- strict thread matches above, loose matches on Subject: below --
2025-05-02 9:37 Stephen Rothwell
2025-05-02 9:44 ` Sudeep Holla
2023-11-30 21:59 Stephen Rothwell
2023-11-30 22:01 ` Sudeep Holla
2023-10-05 23:39 Stephen Rothwell
2023-10-06 6:50 ` Sudeep Holla
2022-11-08 22:29 Stephen Rothwell
2022-11-09 8:58 ` Sudeep Holla
2022-07-01 0:36 Stephen Rothwell
2022-07-01 8:13 ` Sudeep Holla
2020-07-08 23:58 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=20240828101531.38e633d8@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=sudeep.holla@arm.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