[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <EE8EC898-CFE4-4953-968A-ECCEEB09DE76@codeaurora.org>
Date: Tue, 4 Feb 2014 17:51:06 -0600
From: Kumar Gala <galak@...eaurora.org>
To: Stephen Boyd <sboyd@...eaurora.org>
Cc: linux-arm-msm@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Daniel Lezcano <daniel.lezcano@...aro.org>
Subject: Re: [PATCH v2 2/5] clocksource: qcom: Move clocksource code out of mach-msm
On Feb 4, 2014, at 5:09 PM, Stephen Boyd <sboyd@...eaurora.org> wrote:
> On 02/04, Kumar Gala wrote:
>> We intent to share the clocksource code for MSM platforms between legacy
>
> s/intent/intend/
>
>> and multiplatform supported qcom SoCs.
>>
>> Acked-by: Olof Johansson <olof@...om.net>
>> Signed-off-by: Kumar Gala <galak@...eaurora.org>
>
>> diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig
>> index cd6950f..81caa16 100644
>> --- a/drivers/clocksource/Kconfig
>> +++ b/drivers/clocksource/Kconfig
>> @@ -140,3 +140,7 @@ config VF_PIT_TIMER
>> bool
>> help
>> Support for Period Interrupt Timer on Freescale Vybrid Family SoCs.
>> +
>> +config CLKSRC_QCOM
>> + bool
>> + depends on ARCH_MSM
>
> It would be a a little less noisy if you left this as MSM_TIMER
> (msm is all over the code in that file anyway). Also, why do we
> care about depending on ARCH_MSM here? This is a hidden Kconfig
> option anyway.
I will drop the depends, but not sure what point in leaving this as MSM_TIMER.
- k
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists