linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peng Fan <peng.fan@nxp.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Shawn Guo <shawnguo@kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Leonard Crestez <leonard.crestez@nxp.com>
Subject: RE: linux-next: build failure after merge of the imx-mxs tree
Date: Tue, 18 Feb 2020 02:18:00 +0000	[thread overview]
Message-ID: <AM0PR04MB4481EE01C21245B588A9EDAD88110@AM0PR04MB4481.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20200218130859.3deb3404@canb.auug.org.au>


> Subject: linux-next: build failure after merge of the imx-mxs tree

Sorry for this. I'll fix it. It should be the functions not defined when
IMX_SCU not defined.

Thanks,
Peng.

> 
> Hi all,
> 
> After merging the imx-mxs tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
> 
> ld: drivers/soc/imx/soc-imx-scu.o: in function `.imx_scu_soc_probe':
> soc-imx-scu.c:(.text.imx_scu_soc_probe+0x44): undefined reference to
> `.imx_scu_get_handle'
> ld: soc-imx-scu.c:(.text.imx_scu_soc_probe+0x134): undefined reference to
> `.imx_scu_call_rpc'
> ld: soc-imx-scu.c:(.text.imx_scu_soc_probe+0x20c): undefined reference to
> `.imx_scu_call_rpc'
> 
> Caused by commit
> 
>   68c189e3a93c ("soc: imx: increase build coverage for imx8m soc driver")
> 
> I have reverted that commit for today.
> 
> --
> Cheers,
> Stephen Rothwell

  reply	other threads:[~2020-02-18  2:18 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-18  2:08 linux-next: build failure after merge of the imx-mxs tree Stephen Rothwell
2020-02-18  2:18 ` Peng Fan [this message]
2020-02-18  9:38   ` Shawn Guo
  -- strict thread matches above, loose matches on Subject: below --
2023-03-07  1:31 Stephen Rothwell
2022-10-30 22:09 Stephen Rothwell
2022-10-30 22:11 ` Alistair
2022-10-31  0:52   ` Shawn Guo
2021-12-06 22:10 Stephen Rothwell
2021-12-07  7:27 ` Michal Vokáč
2020-11-03  1:00 Stephen Rothwell
2020-11-03  6:39 ` Shawn Guo
2019-12-11 21:35 Stephen Rothwell
2019-12-12  1:33 ` Shawn Guo
2019-12-12  9:45   ` Lucas Stach
2019-12-12 11:37     ` Shawn Guo
2019-05-20 22:37 Stephen Rothwell
2019-05-21  2:16 ` Anson Huang
2019-05-21  4:43   ` Shawn Guo
2019-04-22 22:45 Stephen Rothwell
2019-04-22 22:54 ` Fabio Estevam
2019-04-23  2:12 ` Shawn Guo
2019-01-10 22:30 Stephen Rothwell
2019-01-10 22:56 ` Stephen Rothwell
2019-01-10 23:15   ` Lukasz Majewski
2019-01-12  1:23     ` Shawn Guo
2015-06-01 12:35 Stephen Rothwell
2015-05-29 11:28 Stephen Rothwell
2015-05-29 13:16 ` Shawn Guo

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=AM0PR04MB4481EE01C21245B588A9EDAD88110@AM0PR04MB4481.eurprd04.prod.outlook.com \
    --to=peng.fan@nxp.com \
    --cc=leonard.crestez@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).