All of lore.kernel.org
 help / color / mirror / Atom feed
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: imx: select ARM_CPU_SUSPEND only for imx6
Date: Sun, 28 Feb 2016 11:19:46 +0800	[thread overview]
Message-ID: <20160228031946.GF22051@tiger> (raw)
In-Reply-To: <1456487657-3928107-1-git-send-email-arnd@arndb.de>

On Fri, Feb 26, 2016 at 12:54:12PM +0100, Arnd Bergmann wrote:
> i.MX only needs to select ARM_CPU_SUSPEND manually for the
> very specific case that CONFIG_PM_SLEEP is disabled and imx6
> is used with CONFIG_PM enabled for runtime PM.
> 
> If we are building a kernel only for CPUs that are not using
> the cpu_suspend() helper, we otherwise get a harmless
> build warning:
> 
> warning: (ARCH_MXC && SOC_IMX23 && SOC_IMX28 && ARCH_PXA && MACH_MVEBU_V7 && ARCH_OMAP3 && ARCH_OMAP4 && SOC_OMAP5 && SOC_AM33XX && SOC_DRA7XX && ARCH_EXYNOS3 && ARCH_EXYNOS4 && EXYNOS5420_MCPM && EXYNOS_CPU_SUSPEND && ARCH_VEXPRESS_TC2_PM && ARM_BIG_LITTLE_CPUIDLE && ARM_HIGHBANK_CPUIDLE && QCOM_PM) selects ARM_CPU_SUSPEND which has unmet direct dependencies (ARCH_SUSPEND_POSSIBLE)
> 
> This moves the option to the SOC_IMX6 option that actually
> requires it, in effect reverting commit f36b594f3754 ("ARM:
> mach-imx: Select ARM_CPU_SUSPEND at ARCH_MXC level") that was
> meant as a cleanup and unintentionally caused this warning.
> 
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>

Applied, thanks.

WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Sascha Hauer <kernel@pengutronix.de>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: imx: select ARM_CPU_SUSPEND only for imx6
Date: Sun, 28 Feb 2016 11:19:46 +0800	[thread overview]
Message-ID: <20160228031946.GF22051@tiger> (raw)
In-Reply-To: <1456487657-3928107-1-git-send-email-arnd@arndb.de>

On Fri, Feb 26, 2016 at 12:54:12PM +0100, Arnd Bergmann wrote:
> i.MX only needs to select ARM_CPU_SUSPEND manually for the
> very specific case that CONFIG_PM_SLEEP is disabled and imx6
> is used with CONFIG_PM enabled for runtime PM.
> 
> If we are building a kernel only for CPUs that are not using
> the cpu_suspend() helper, we otherwise get a harmless
> build warning:
> 
> warning: (ARCH_MXC && SOC_IMX23 && SOC_IMX28 && ARCH_PXA && MACH_MVEBU_V7 && ARCH_OMAP3 && ARCH_OMAP4 && SOC_OMAP5 && SOC_AM33XX && SOC_DRA7XX && ARCH_EXYNOS3 && ARCH_EXYNOS4 && EXYNOS5420_MCPM && EXYNOS_CPU_SUSPEND && ARCH_VEXPRESS_TC2_PM && ARM_BIG_LITTLE_CPUIDLE && ARM_HIGHBANK_CPUIDLE && QCOM_PM) selects ARM_CPU_SUSPEND which has unmet direct dependencies (ARCH_SUSPEND_POSSIBLE)
> 
> This moves the option to the SOC_IMX6 option that actually
> requires it, in effect reverting commit f36b594f3754 ("ARM:
> mach-imx: Select ARM_CPU_SUSPEND at ARCH_MXC level") that was
> meant as a cleanup and unintentionally caused this warning.
> 
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>

Applied, thanks.

  reply	other threads:[~2016-02-28  3:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26 11:54 [PATCH] ARM: imx: select ARM_CPU_SUSPEND only for imx6 Arnd Bergmann
2016-02-26 11:54 ` Arnd Bergmann
2016-02-28  3:19 ` Shawn Guo [this message]
2016-02-28  3:19   ` 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=20160228031946.GF22051@tiger \
    --to=shawnguo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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 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.