From: Shawn Guo <shawnguo@kernel.org>
To: Yue Haibing <yuehaibing@huawei.com>
Cc: aisheng.dong@nxp.com, abel.vesa@nxp.com, Anson.Huang@nxp.com,
catalin.marinas@arm.com, s.hauer@pengutronix.de,
will.deacon@arm.com, linux-kernel@vger.kernel.org,
linux-imx@nxp.com, kernel@pengutronix.de,
leonard.crestez@nxp.com, festevam@gmail.com,
linux-arm-kernel@lists.infradead.org, l.stach@pengutronix.de
Subject: Re: [PATCH v2] soc: imx: Fix build error without CONFIG_SOC_BUS
Date: Sun, 12 May 2019 09:21:36 +0800 [thread overview]
Message-ID: <20190512012134.GL15856@dragon> (raw)
In-Reply-To: <20190424091517.41428-1-yuehaibing@huawei.com>
On Wed, Apr 24, 2019 at 05:15:17PM +0800, Yue Haibing wrote:
> From: YueHaibing <yuehaibing@huawei.com>
>
> During randconfig builds, I occasionally run into an invalid configuration
>
> drivers/soc/imx/soc-imx8.o: In function `imx8_soc_init':
> soc-imx8.c:(.init.text+0x144): undefined reference to `soc_device_register'
>
> while CONFIG_SOC_BUS is not set, the building failed like this. This patch
> selects SOC_BUS to fix it.
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Fixes: a7e26f356ca1 ("soc: imx: Add generic i.MX8 SoC driver")
> Suggested-by: Leonard Crestez <leonard.crestez@nxp.com>
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> ---
> v2: select SOC_BUS from CONFIG_ARCH_MXC directly
> ---
So this becomes a 'arm64: imx: ' change. I updated the subject prefix
and applied the patch.
Shawn
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Yue Haibing <yuehaibing@huawei.com>
Cc: s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com, l.stach@pengutronix.de,
aisheng.dong@nxp.com, leonard.crestez@nxp.com, abel.vesa@nxp.com,
Anson.Huang@nxp.com, catalin.marinas@arm.com,
will.deacon@arm.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] soc: imx: Fix build error without CONFIG_SOC_BUS
Date: Sun, 12 May 2019 09:21:36 +0800 [thread overview]
Message-ID: <20190512012134.GL15856@dragon> (raw)
In-Reply-To: <20190424091517.41428-1-yuehaibing@huawei.com>
On Wed, Apr 24, 2019 at 05:15:17PM +0800, Yue Haibing wrote:
> From: YueHaibing <yuehaibing@huawei.com>
>
> During randconfig builds, I occasionally run into an invalid configuration
>
> drivers/soc/imx/soc-imx8.o: In function `imx8_soc_init':
> soc-imx8.c:(.init.text+0x144): undefined reference to `soc_device_register'
>
> while CONFIG_SOC_BUS is not set, the building failed like this. This patch
> selects SOC_BUS to fix it.
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Fixes: a7e26f356ca1 ("soc: imx: Add generic i.MX8 SoC driver")
> Suggested-by: Leonard Crestez <leonard.crestez@nxp.com>
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> ---
> v2: select SOC_BUS from CONFIG_ARCH_MXC directly
> ---
So this becomes a 'arm64: imx: ' change. I updated the subject prefix
and applied the patch.
Shawn
next prev parent reply other threads:[~2019-05-12 1:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 7:59 [PATCH] soc: imx: Fix build error without CONFIG_SOC_BUS Yue Haibing
2019-04-24 7:59 ` Yue Haibing
2019-04-24 8:11 ` Leonard Crestez
2019-04-24 8:11 ` Leonard Crestez
2019-04-24 8:47 ` YueHaibing
2019-04-24 8:47 ` YueHaibing
2019-04-24 9:15 ` [PATCH v2] " Yue Haibing
2019-04-24 9:15 ` Yue Haibing
2019-04-24 10:00 ` Leonard Crestez
2019-04-24 10:00 ` Leonard Crestez
2019-05-12 1:21 ` Shawn Guo [this message]
2019-05-12 1:21 ` 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=20190512012134.GL15856@dragon \
--to=shawnguo@kernel.org \
--cc=Anson.Huang@nxp.com \
--cc=abel.vesa@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=catalin.marinas@arm.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=leonard.crestez@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=will.deacon@arm.com \
--cc=yuehaibing@huawei.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 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.