From: "Horia Geantă" <horia.geanta@nxp.com>
To: Peng Fan <peng.fan@nxp.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>
Cc: "kernel@pengutronix.de" <kernel@pengutronix.de>,
"festevam@gmail.com" <festevam@gmail.com>,
dl-linux-imx <linux-imx@nxp.com>,
"allison@lohutok.net" <allison@lohutok.net>,
"info@metux.net" <info@metux.net>,
Anson Huang <anson.huang@nxp.com>,
Leonard Crestez <leonard.crestez@nxp.com>,
"git@andred.net" <git@andred.net>, Abel Vesa <abel.vesa@nxp.com>,
"andrew.smirnov@gmail.com" <andrew.smirnov@gmail.com>,
"cphealy@gmail.com" <cphealy@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Alison Wang <alison.wang@nxp.com>
Subject: Re: [PATCH V3 0/3] ARM: imx: move cpu code to drivers/soc/imx
Date: Sun, 5 Jul 2020 12:47:03 +0300 [thread overview]
Message-ID: <03737ac7-75c8-05d7-e0b0-3af470e3b6b8@nxp.com> (raw)
In-Reply-To: <DB6PR0402MB27604DD8AF73824C3972BC90886A0@DB6PR0402MB2760.eurprd04.prod.outlook.com>
On 7/3/2020 3:25 PM, Peng Fan wrote:
> Sorry to break LS1021A. But I wonder why i.MX code would affect LS?
>
imx_soc_device_init() was modified to be called for all SoCs under ARCH_MXC.
multi_v7_defconfig, which is used for LS1021A, selects ARCH_MXC.
Previously imx_soc_device_init() was called only for i.MX (and Vybrid) SoCs.
Horia
prev parent reply other threads:[~2020-07-05 9:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 5:51 peng.fan
2020-05-20 5:51 ` [PATCH V3 1/3] ARM: imx: use device_initcall for imx_soc_device_init peng.fan
2020-10-28 13:28 ` Rob Herring
2020-10-28 13:57 ` Peng Fan
2020-05-20 5:51 ` [PATCH V3 2/3] ARM: imx: move cpu definitions into a header peng.fan
2020-05-20 5:51 ` [PATCH V3 3/3] soc: imx: move cpu code to drivers/soc/imx peng.fan
2020-05-20 15:11 ` [PATCH V3 0/3] ARM: " Shawn Guo
2020-07-03 8:53 ` Horia Geantă
2020-07-03 12:25 ` Peng Fan
2020-07-05 9:47 ` Horia Geantă [this message]
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=03737ac7-75c8-05d7-e0b0-3af470e3b6b8@nxp.com \
--to=horia.geanta@nxp.com \
--cc=abel.vesa@nxp.com \
--cc=alison.wang@nxp.com \
--cc=allison@lohutok.net \
--cc=andrew.smirnov@gmail.com \
--cc=anson.huang@nxp.com \
--cc=cphealy@gmail.com \
--cc=festevam@gmail.com \
--cc=git@andred.net \
--cc=info@metux.net \
--cc=kernel@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=peng.fan@nxp.com \
--cc=s.hauer@pengutronix.de \
--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
all inboxes | Powered by JetHome®