From: Shawn Guo <shawnguo@kernel.org>
To: Peng Fan <peng.fan@nxp.com>
Cc: "s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"arnd@arndb.de" <arnd@arndb.de>,
"festevam@gmail.com" <festevam@gmail.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
dl-linux-imx <linux-imx@nxp.com>,
"olof@lixom.net" <olof@lixom.net>,
Aisheng Dong <aisheng.dong@nxp.com>,
Leonard Crestez <leonard.crestez@nxp.com>,
Abel Vesa <abel.vesa@nxp.com>,
"krzk@kernel.org" <krzk@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V3 2/2] soc: imx: increase build coverage for imx8m soc driver
Date: Fri, 14 Feb 2020 10:44:14 +0800 [thread overview]
Message-ID: <20200214024414.GG22842@dragon> (raw)
In-Reply-To: <1580191098-5886-3-git-send-email-peng.fan@nxp.com>
On Tue, Jan 28, 2020 at 06:03:17AM +0000, Peng Fan wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> The soc-imx8.c driver is actually for i.MX8M family, so rename it
> to soc-imx8m.c.
>
> Use CONFIG_SOC_IMX8M as build gate, not CONFIG_ARCH_MXC, to control
> whether build this driver, also make it possible for compile test.
>
> Default set it to y for ARCH_MXC && ARM64
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
Applied, thanks.
prev parent reply other threads:[~2020-02-14 2:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 6:03 [PATCH V3 0/2] soc: imx: increase build coverage for imx8 soc driver Peng Fan
2020-01-28 6:03 ` [PATCH V3 1/2] soc: imx: gpcv2: include linux/sizes.h Peng Fan
2020-01-28 6:03 ` [PATCH V3 2/2] soc: imx: increase build coverage for imx8m soc driver Peng Fan
2020-01-28 14:35 ` Leonard Crestez
2020-02-14 2:44 ` Shawn Guo [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=20200214024414.GG22842@dragon \
--to=shawnguo@kernel.org \
--cc=abel.vesa@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=arnd@arndb.de \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzk@kernel.org \
--cc=leonard.crestez@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=peng.fan@nxp.com \
--cc=s.hauer@pengutronix.de \
/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).