From: Sudeep Holla <sudeep.holla@arm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Peng Fan <peng.fan@nxp.com>, Sudeep Holla <sudeep.holla@arm.com>,
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 scmi tree
Date: Wed, 28 Aug 2024 09:48:57 +0100 [thread overview]
Message-ID: <Zs7kebuQ363_IHia@bogus> (raw)
In-Reply-To: <20240828101531.38e633d8@canb.auug.org.au>
On Wed, Aug 28, 2024 at 10:15:31AM +1000, Stephen Rothwell wrote:
> 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.
>
Sorry for that, it will be fixed for tomorrow. Thanks for the report.
--
Regards,
Sudeep
next prev parent reply other threads:[~2024-08-28 8:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 0:15 linux-next: build failure after merge of the scmi tree Stephen Rothwell
2024-08-28 5:29 ` Peng Fan
2024-08-28 8:48 ` Sudeep Holla [this message]
-- 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=Zs7kebuQ363_IHia@bogus \
--to=sudeep.holla@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=sfr@canb.auug.org.au \
/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.