Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755503Ab3IZIIN (ORCPT ); Thu, 26 Sep 2013 04:08:13 -0400 Received: from mail-ea0-f172.google.com ([209.85.215.172]:59875 "EHLO mail-ea0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751198Ab3IZIII (ORCPT ); Thu, 26 Sep 2013 04:08:08 -0400 From: Tomasz Figa To: linux-arm-kernel@lists.infradead.org Cc: Sebastian Hesselbarth , linux-samsung-soc@vger.kernel.org, Russell King , Arnd Bergmann , linux-kernel@vger.kernel.org, Kukjin Kim , Olof Johansson Subject: Re: [PATCH 12/26] ARM: exynos: remove custom .init_time hook Date: Thu, 26 Sep 2013 10:08:03 +0200 Message-ID: <1573378.EKN2gyy8Sh@flatron> User-Agent: KMail/4.11.1 (Linux/3.11.1-gentoo; KDE/4.11.1; x86_64; ; ) In-Reply-To: <5243D267.3010704@gmail.com> References: <1379526839-14798-1-git-send-email-sebastian.hesselbarth@gmail.com> <1379526839-14798-13-git-send-email-sebastian.hesselbarth@gmail.com> <5243D267.3010704@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 932 Lines: 29 Hi Sebastian, On Thursday 26 of September 2013 08:21:27 Sebastian Hesselbarth wrote: > On 09/18/2013 07:53 PM, Sebastian Hesselbarth wrote: > > With arch/arm calling of_clk_init(NULL) from time_init(), we can now > > remove custom .init_time hooks. While at it, also remove some now > > redundant includes. > > > > Signed-off-by: Sebastian Hesselbarth > > --- > > Ping, This patch looks fine to me (as the whole series). Reviewed-by: Tomasz Figa I don't see any reason why this series could introduce a regression on Exynos SoCs, but just in case let me test it on selected Exynos4 and Exynos5 boards. Best regards, Tomasz -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/