Received: by 10.223.185.116 with SMTP id b49csp2271911wrg; Thu, 22 Feb 2018 10:53:42 -0800 (PST) X-Google-Smtp-Source: AH8x2242u6Fa/87Uvy0qHeI6jrJ3vXgAvDAGB3gkArDT9maEFogSN3etvtN7ayEucwiSwif2HlvJ X-Received: by 2002:a17:902:ac1:: with SMTP id 59-v6mr7445619plp.228.1519325622651; Thu, 22 Feb 2018 10:53:42 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519325622; cv=none; d=google.com; s=arc-20160816; b=sdBAC1asEMdTwtTvfax18ND1e69LyXCO4uKSptl3mYCbZo6j9NqQAZAHVFUmR94/ja MGk5iUvb8VHZnhnrPCSRcuUv9h+U15Gko1kbRxYeWnH1QEuxUfb5eG8fd0ZiPIaSLlRS surN1l3IeAE74P8YKR/X1KtUI33mRgA6peZ0DnRL+h16MUX46ZCs+b1VkmtF8xTVmG9P IIZ1PpEiT16h7pWGeTpsijn08s4z6VrU0tz/FEsTU5clCPXQramYEWu0Y/gSChRto1zB guT1CrfZSG7z1l5por4NJb9sv6BVBM5t9kwAi6aoIc4Nriy8vCol/o5pvOJFDvZNiS+q 3XKg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=7MXoSiS3dD/xPZ7fsMhRkkZWu9iJ4IZRI1oUVldEBsI=; b=HYzPMif7lJXF4jEu4+UBQ1wLLefuM/G+I8cT2DQi2puK5FX4hApWpNDxGkhSSx2IOF l30ALWXbkMnkGoXOYtGavgys/tvyeTHcSF3+/hwNMBDYgn/Z2hBIomX7RfYlmJk+r7dv htJb85G3gcC7k+ZVrWTsx2Znf2b3mCdbBNw6c7XKHaVyyLbXaZ8FP2VX1cg0HDq+NcbN 6pts+G92nQW8zkiscKW8LiAeqfpMnUW4voQreuCnU2a1xJRg4l/bvAwU56WmEHVBTdZ7 j4CU8Uz8nyZvwIc+/hjx8h7/UA8CnhS0DdeIiVEu6eKyqaUWv6ZJOxTNRA1z3mcKHWrG jEfA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e39-v6si438258plg.364.2018.02.22.10.53.27; Thu, 22 Feb 2018 10:53:42 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751346AbeBVSwW (ORCPT + 99 others); Thu, 22 Feb 2018 13:52:22 -0500 Received: from muru.com ([72.249.23.125]:57876 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750816AbeBVSwV (ORCPT ); Thu, 22 Feb 2018 13:52:21 -0500 Received: from atomide.com (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id C88AF80FA; Thu, 22 Feb 2018 18:46:27 +0000 (UTC) Date: Thu, 22 Feb 2018 10:45:42 -0800 From: Tony Lindgren To: Ladislav Michl Cc: Keerthy , daniel.lezcano@linaro.org, thierry.reding@gmail.com, aaro.koskinen@iki.fi, Claudiu.Beznea@microchip.com, narmstrong@baylibre.com, linux-pwm@vger.kernel.org, s-anna@ti.com, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, sebastian.reichel@collabora.co.uk, linux-omap@vger.kernel.org, robh+dt@kernel.org, t-kristo@ti.com, grygorii.strashko@ti.com Subject: Re: [PATCH v11 04/10] clocksource: timer-ti-dm: Replace architecture Message-ID: <20180222184541.GB5184@atomide.com> References: <1518674511-26421-1-git-send-email-j-keerthy@ti.com> <1518674511-26421-5-git-send-email-j-keerthy@ti.com> <20180222105713.GA30885@lenoch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180222105713.GA30885@lenoch> User-Agent: Mutt/1.9.3 (2018-01-21) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Ladislav Michl [180222 10:58]: > On Thu, Feb 15, 2018 at 11:31:45AM +0530, Keerthy wrote: > > Replace architecture specific guard with clocksource guard. > > > > Signed-off-by: Keerthy > > Replace architecture specific defines with clocksource > > This looks like a bit unussual commit log. Also, what about merging > it with previous patch? I'll just remove that line locally to avoid yet another set of patches being posted :) > Btw, I tested whole serie again on the top of today's -next and it is > still working fine. What is preventing these patches from being merged? Well I noticed we need a fix for omap1 that I just posted. And patch 4/10 needs the following select for omap16xx that I'll fold in. I'll push it all to omap-for-v4.17/timer and will merge into my for-next after some more testing. It seems any further patching can be done after move to drivers. Regards, Tony 8< ----------------- --- a/arch/arm/mach-omap1/Kconfig +++ b/arch/arm/mach-omap1/Kconfig @@ -30,6 +30,7 @@ config ARCH_OMAP16XX bool "OMAP16xx Based System" select ARCH_OMAP_OTG select CPU_ARM926T + select OMAP_DM_TIMER config OMAP_MUX bool "OMAP multiplexing support"