From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: [PATCH v3 0/3] Remove ARCH_MSM* configs Date: Tue, 01 Dec 2015 12:50:29 +0100 Message-ID: <4507574.IoXDhs75Z7@wuerfel> References: <1448933123-9843-1-git-send-email-sboyd@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Return-path: Received: from mout.kundenserver.de ([217.72.192.75]:54924 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755004AbbLALvE (ORCPT ); Tue, 1 Dec 2015 06:51:04 -0500 In-Reply-To: <1448933123-9843-1-git-send-email-sboyd@codeaurora.org> Sender: linux-arm-msm-owner@vger.kernel.org List-Id: linux-arm-msm@vger.kernel.org To: linux-arm-kernel@lists.infradead.org Cc: Stephen Boyd , Andy Gross , linux-arm-msm@vger.kernel.org, Daniel Lezcano , linux-kernel@vger.kernel.org On Monday 30 November 2015 17:25:20 Stephen Boyd wrote: > This patch series allows us to remove the ARCH_MSM* configs that live > in mach-qcom/Kconfig. They're mostly proxy configs for user selectable > clocksource configurations anyway. > > Acked-by: Arnd Bergmann I suppose we could have a QCOM_B_FAMILY option as well, but it looks like we don't need that. Maybe mention in the help text that B_FAMILY is always supported. Arnd From mboxrd@z Thu Jan 1 00:00:00 1970 From: arnd@arndb.de (Arnd Bergmann) Date: Tue, 01 Dec 2015 12:50:29 +0100 Subject: [PATCH v3 0/3] Remove ARCH_MSM* configs In-Reply-To: <1448933123-9843-1-git-send-email-sboyd@codeaurora.org> References: <1448933123-9843-1-git-send-email-sboyd@codeaurora.org> Message-ID: <4507574.IoXDhs75Z7@wuerfel> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Monday 30 November 2015 17:25:20 Stephen Boyd wrote: > This patch series allows us to remove the ARCH_MSM* configs that live > in mach-qcom/Kconfig. They're mostly proxy configs for user selectable > clocksource configurations anyway. > > Acked-by: Arnd Bergmann I suppose we could have a QCOM_B_FAMILY option as well, but it looks like we don't need that. Maybe mention in the help text that B_FAMILY is always supported. Arnd