linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] ARM: OMAP5: Fix build for PM code
Date: Wed, 26 Oct 2016 08:16:59 -0700	[thread overview]
Message-ID: <20161026151703.24730-2-tony@atomide.com> (raw)
In-Reply-To: <20161026151703.24730-1-tony@atomide.com>

It's CONFIG_SOC_OMAP5, not CONFIG_ARCH_OMAP5. Looks like make randconfig
builds have not hit this one yet.

Fixes: b3bf289c1c45 ("ARM: OMAP2+: Fix build with CONFIG_SMP and CONFIG_PM
is not set")
Signed-off-by: Tony Lindgren <tony@atomide.com>
---
 arch/arm/mach-omap2/Makefile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm/mach-omap2/Makefile b/arch/arm/mach-omap2/Makefile
--- a/arch/arm/mach-omap2/Makefile
+++ b/arch/arm/mach-omap2/Makefile
@@ -80,7 +80,7 @@ endif
 # Power Management
 omap-4-5-pm-common			= omap-mpuss-lowpower.o
 obj-$(CONFIG_ARCH_OMAP4)		+= $(omap-4-5-pm-common)
-obj-$(CONFIG_ARCH_OMAP5)		+= $(omap-4-5-pm-common)
+obj-$(CONFIG_SOC_OMAP5)			+= $(omap-4-5-pm-common)
 obj-$(CONFIG_OMAP_PM_NOOP)		+= omap-pm-noop.o
 
 ifeq ($(CONFIG_PM),y)
-- 
2.9.3

  reply	other threads:[~2016-10-26 15:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-26 15:16 [PATCH 0/5] Minimal cpuidle fixes for omap5 and dra7 Tony Lindgren
2016-10-26 15:16 ` Tony Lindgren [this message]
2016-10-26 15:17 ` [PATCH 2/5] ARM: OMAP5: Fix mpuss_early_init Tony Lindgren
2016-10-26 20:21   ` Tony Lindgren
2016-10-26 15:17 ` [PATCH 3/5] ARM: OMAP4+: Fix bad fallthrough for cpuidle Tony Lindgren
2016-10-26 15:17 ` [PATCH 4/5] ARM: DRA7: PM: cpuidle MPU CSWR support Tony Lindgren
2016-10-27 16:15   ` Tony Lindgren
2016-10-26 15:17 ` [PATCH 5/5] ARM: OMAP5: Enable minimal cpuidle for omap5 retention Tony Lindgren
2016-10-26 19:53 ` [PATCH 0/5] Minimal cpuidle fixes for omap5 and dra7 Santosh Shilimkar
2016-10-26 20:56 ` Nishanth Menon
2016-10-26 21:31   ` Tony Lindgren
2016-10-27  7:43 ` H. Nikolaus Schaller

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=20161026151703.24730-2-tony@atomide.com \
    --to=tony@atomide.com \
    --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 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).