Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754154AbcKOS7s (ORCPT ); Tue, 15 Nov 2016 13:59:48 -0500 Received: from mail-wm0-f65.google.com ([74.125.82.65]:35920 "EHLO mail-wm0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752754AbcKOS7q (ORCPT ); Tue, 15 Nov 2016 13:59:46 -0500 Date: Tue, 15 Nov 2016 20:59:39 +0200 From: Krzysztof Kozlowski To: Pankaj Dubey Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, rmk+kernel@armlinux.org.uk, arnd@arndb.de, horms@verge.net.au, magnus.damm@gmail.com, geert+renesas@glider.be, vireshk@kernel.org, shiraz.linux.kernel@gmail.com, krzk@kernel.org, thomas.ab@samsung.com, linux-samsung-soc@vger.kernel.org Subject: Re: [PATCH 02/16] ARM: EXYNOS: use generic API to enable SCU Message-ID: <20161115185939.GA14626@kozik-lap> References: <1479099731-28108-1-git-send-email-pankaj.dubey@samsung.com> <1479099731-28108-3-git-send-email-pankaj.dubey@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1479099731-28108-3-git-send-email-pankaj.dubey@samsung.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1014 Lines: 28 On Mon, Nov 14, 2016 at 10:31:57AM +0530, Pankaj Dubey wrote: > Now as we have of_scu_enable which takes care of mapping > scu base from DT, lets use it. > > This patch also fixes build failure in case !SMP caused > by commit SHA ID: 94210b1abb2 which is already merged in > krzk/for-next branch > > CC: Krzysztof Kozlowski > CC: linux-samsung-soc@vger.kernel.org > Signed-off-by: Pankaj Dubey > --- > arch/arm/mach-exynos/common.h | 1 - > arch/arm/mach-exynos/platsmp.c | 30 ++++-------------------------- > arch/arm/mach-exynos/pm.c | 4 ++-- > arch/arm/mach-exynos/suspend.c | 14 ++++---------- > 4 files changed, 10 insertions(+), 39 deletions(-) > Looks correct, for reference: Reviewed-by: Krzysztof Kozlowski However this depends on changes in my next/soc branch (and these changes were the trigger for this patchset). I can either provide a tag with Exynos commits or accept one with common SCU code. Best regards, Krzysztof