From: Sudeep Holla <sudeep.holla@arm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Cristian Marussi <cristian.marussi@arm.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, 9 Nov 2022 08:58:23 +0000 [thread overview]
Message-ID: <20221109085823.qixqq47z2fr7wivv@bogus> (raw)
In-Reply-To: <20221109092901.0c748a3e@canb.auug.org.au>
Hi Stephen,
On Wed, Nov 09, 2022 at 09:29:01AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the scmi tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> ERROR: modpost: "debugfs_create_str" [drivers/firmware/arm_scmi/scmi-module.ko] undefined!
>
> Caused by commit
>
> 4ccdc880f1bb ("firmware: arm_scmi: Add core Raw transmission support")
>
> I have used the scmi tree from next-20221108 for today.
>
Sorry for that, and thanks for identifying and dropping it in -next.
I will drop the changes until we have fixed it.
--
Regards,
Sudeep
next prev parent reply other threads:[~2022-11-09 8:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 22:29 linux-next: build failure after merge of the scmi tree Stephen Rothwell
2022-11-09 8:58 ` Sudeep Holla [this message]
-- strict thread matches above, loose matches on Subject: below --
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-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=20221109085823.qixqq47z2fr7wivv@bogus \
--to=sudeep.holla@arm.com \
--cc=cristian.marussi@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).