From: Leonard Crestez <leonard.crestez@nxp.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Chanwoo Choi <cw00.choi@samsung.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the devfreq tree
Date: Fri, 22 Nov 2019 21:54:43 +0000 [thread overview]
Message-ID: <VI1PR04MB7023AA4F1583DB3C279F90F5EE490@VI1PR04MB7023.eurprd04.prod.outlook.com> (raw)
In-Reply-To: 20191122155941.4c8e3bd1@canb.auug.org.au
On 2019-11-22 6:59 AM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the devfreq tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> ERROR: "__arm_smccc_smc" [drivers/devfreq/imx8m-ddrc.ko] undefined!
>
> Caused by commit
>
> 1fcfb874236e ("PM / devfreq: Add dynamic scaling for imx8m ddr controller")
Sorry about this, it seems smccc calls fail under COMPILE_TEST. Fix is
to add explicit dependency on HAVE_ARM_SMCCC
Resent entire series: https://patchwork.kernel.org/cover/11258499/
--
Regards,
Leonard
next prev parent reply other threads:[~2019-11-22 21:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 4:59 linux-next: build failure after merge of the devfreq tree Stephen Rothwell
2019-11-22 21:54 ` Leonard Crestez [this message]
2019-12-13 1:49 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=VI1PR04MB7023AA4F1583DB3C279F90F5EE490@VI1PR04MB7023.eurprd04.prod.outlook.com \
--to=leonard.crestez@nxp.com \
--cc=cw00.choi@samsung.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).