From: Shawn Guo <shawnguo@kernel.org>
To: peng.fan@nxp.com
Cc: aisheng.dong@nxp.com, abel.vesa@nxp.com, s.hauer@pengutronix.de,
linux-kernel@vger.kernel.org, krzk@kernel.org, linux-imx@nxp.com,
kernel@pengutronix.de, olof@lixom.net, leonard.crestez@nxp.com,
festevam@gmail.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V5 0/2] soc: imx: increase build coverage for imx8 soc driver
Date: Tue, 10 Mar 2020 14:55:22 +0800 [thread overview]
Message-ID: <20200310065521.GA17772@dragon> (raw)
In-Reply-To: <1582252339-15733-1-git-send-email-peng.fan@nxp.com>
On Fri, Feb 21, 2020 at 10:32:17AM +0800, peng.fan@nxp.com wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> V5:
> Add missed "static inline" in misc.h
>
> V4:
> Add dummy functions to fix build issue when soc-imx-scu.c built in,
> but drivers/firmware/imx/imx-scu.c not built in.
> No change to Patch 2/2.
>
> V3:
> Per Arnd's suggestions, merged Patch 2/3/4/5 into one patch
> Dropped the defconfig change with a default Kconfig
>
> Leonard, I dropped you R-b in V3 since the change.
>
> V2:
> Include Leonard's patch to fix build break after enable compile test
> Add Leonard's R-b tag
>
> 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 (2):
> firmware: imx: add dummy functions
> soc: imx: increase build coverage for imx8m soc driver
Applied both, thanks.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-03-10 6:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 2:32 [PATCH V5 0/2] soc: imx: increase build coverage for imx8 soc driver peng.fan
2020-02-21 2:32 ` [PATCH V5 1/2] firmware: imx: add dummy functions peng.fan
2020-02-21 2:32 ` [PATCH V5 2/2] soc: imx: increase build coverage for imx8m soc driver peng.fan
2020-03-10 6:55 ` 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=20200310065521.GA17772@dragon \
--to=shawnguo@kernel.org \
--cc=abel.vesa@nxp.com \
--cc=aisheng.dong@nxp.com \
--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).