Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753593AbbFLIWu (ORCPT ); Fri, 12 Jun 2015 04:22:50 -0400 Received: from mx08-00178001.pphosted.com ([91.207.212.93]:53259 "EHLO mx08-00178001.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751616AbbFLIWq (ORCPT ); Fri, 12 Jun 2015 04:22:46 -0400 Message-ID: <557A96C9.1050308@st.com> Date: Fri, 12 Jun 2015 10:22:33 +0200 From: Maxime Coquelin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Viresh Kumar , Thomas Gleixner , Daniel Lezcano CC: , , Srinivas Kandagatla , Patrice Chotard Subject: Re: [PATCH V2 3/7] clocksource: arm_global_timer: Migrate to new 'set-state' interface References: In-Reply-To: Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.201.23.80] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.14.151,1.0.33,0.0.0000 definitions=2015-06-12_01:2015-06-11,2015-06-12,1970-01-01 signatures=0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1075 Lines: 32 Hi Viresh, On 06/12/2015 10:00 AM, Viresh Kumar wrote: > Migrate arm_global_timer driver to the new 'set-state' interface > provided by the clockevents core, the earlier 'set-mode' interface is > marked obsolete now. > > This also enables us to implement callbacks for new states of clockevent > devices, for example: ONESHOT_STOPPED. > > Acked-by: Daniel Lezcano > Cc: Srinivas Kandagatla > Cc: Maxime Coquelin > Cc: Patrice Chotard > Signed-off-by: Viresh Kumar > --- > drivers/clocksource/arm_global_timer.c | 37 ++++++++++++++++------------------ > 1 file changed, 17 insertions(+), 20 deletions(-) > > You can add: Acked-by: Maxime Coquelin Thanks! Maxime -- 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/