linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leonard Crestez <leonard.crestez@nxp.com>
To: Peng Fan <peng.fan@nxp.com>, "shawnguo@kernel.org" <shawnguo@kernel.org>
Cc: "catalin.marinas@arm.com" <catalin.marinas@arm.com>,
	"will@kernel.org" <will@kernel.org>,
	"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>,
	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 0/4] soc: imx: increase build coverage for imx8 soc driver
Date: Mon, 20 Jan 2020 12:45:03 +0000	[thread overview]
Message-ID: <VI1PR04MB70231E81AB33489264502009EE320@VI1PR04MB7023.eurprd04.prod.outlook.com> (raw)
In-Reply-To: 1579146280-1750-1-git-send-email-peng.fan@nxp.com

On 16.01.2020 05:48, Peng Fan wrote:
> From: Peng Fan <peng.fan@nxp.com>
> 
> Rename soc-imx8.c to soc-imx8m.c which is for i.MX8M family
> Add SOC_IMX8M for build gate soc-imx8m.c
> Increase build coverage for i.MX SoC driver
> 
> Peng Fan (4):
>    soc: imx: Kconfig: add SOC_IMX8M entry
>    arm64: defconfig: Enable CONFIG_SOC_IMX8M by default
>    soc: Makefile: increase build coverage for i.MX
>    soc: imx: Use CONFIG_SOC_IMX8M as build gate
> 
>   arch/arm64/configs/defconfig                | 1 +
>   drivers/soc/Makefile                        | 2 +-
>   drivers/soc/imx/Kconfig                     | 8 ++++++++
>   drivers/soc/imx/Makefile                    | 2 +-
>   drivers/soc/imx/{soc-imx8.c => soc-imx8m.c} | 0
>   5 files changed, 11 insertions(+), 2 deletions(-)
>   rename drivers/soc/imx/{soc-imx8.c => soc-imx8m.c} (100%)

I applied your patches and compiletest failed for me on x86:

../drivers/soc/imx/gpcv2.c: In function ‘imx_gpcv2_probe’:
../drivers/soc/imx/gpcv2.c:561:21: error: ‘SZ_4K’ undeclared (first use 
in this function)
    .max_register   = SZ_4K,
                      ^~~~~
../drivers/soc/imx/gpcv2.c:561:21: note: each undeclared identifier is 
reported only once for each function it appears in

It seems that on x86 <linux/sizes.h> needs to be included explicitly 
while on arm it is already included indirectly through arch headers. Fix 
is very simple:

diff --git drivers/soc/imx/gpcv2.c drivers/soc/imx/gpcv2.c
index b0dffb06c05d..6cf8a7a412bd 100644
--- drivers/soc/imx/gpcv2.c
+++ drivers/soc/imx/gpcv2.c
@@ -14,6 +14,7 @@
  #include <linux/pm_domain.h>
  #include <linux/regmap.h>
  #include <linux/regulator/consumer.h>
+#include <linux/sizes.h>
  #include <dt-bindings/power/imx7-power.h>
  #include <dt-bindings/power/imx8mq-power.h>

---

My test looks like this:

make O=build_compiletest defconfig
make O=build_compiletest allmodconfig
echo CONFIG_COMPILE_TEST=y >> build_compiletest/.config
make O=build_compiletest "$@"

Other than this:

Reviewed-by: Leonard Crestez <leonard.crestez@nxp.com>

      parent reply	other threads:[~2020-01-20 12:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16  3:48 [PATCH 0/4] soc: imx: increase build coverage for imx8 soc driver Peng Fan
2020-01-16  3:49 ` [PATCH 1/4] soc: imx: Kconfig: add SOC_IMX8M entry Peng Fan
2020-01-16  3:49 ` [PATCH 2/4] arm64: defconfig: Enable CONFIG_SOC_IMX8M by default Peng Fan
2020-01-16  3:49 ` [PATCH 3/4] soc: Makefile: increase build coverage for i.MX Peng Fan
2020-01-18  8:38   ` kbuild test robot
2020-01-16  3:49 ` [PATCH 4/4] soc: imx: Use CONFIG_SOC_IMX8M as build gate Peng Fan
2020-01-20 12:45 ` Leonard Crestez [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=VI1PR04MB70231E81AB33489264502009EE320@VI1PR04MB7023.eurprd04.prod.outlook.com \
    --to=leonard.crestez@nxp.com \
    --cc=abel.vesa@nxp.com \
    --cc=aisheng.dong@nxp.com \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=krzk@kernel.org \
    --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 \
    --cc=shawnguo@kernel.org \
    --cc=will@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).