Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755941AbbGUW26 (ORCPT ); Tue, 21 Jul 2015 18:28:58 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:38537 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754044AbbGUW24 (ORCPT ); Tue, 21 Jul 2015 18:28:56 -0400 Date: Tue, 21 Jul 2015 17:28:51 -0500 From: rkuo To: Viresh Kumar Cc: Thomas Gleixner , Daniel Lezcano , linaro-kernel@lists.linaro.org, linux-kernel@vger.kernel.org, linux-hexagon@vger.kernel.org Subject: Re: [PATCH 07/23] hexagon/time: Migrate to new 'set-state' interface Message-ID: <20150721222851.GB29874@codeaurora.org> References: <519cb907e596d13b9f1e3fd1ee689acbbbeb56c7.1437044517.git.viresh.kumar@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <519cb907e596d13b9f1e3fd1ee689acbbbeb56c7.1437044517.git.viresh.kumar@linaro.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1181 Lines: 32 On Thu, Jul 16, 2015 at 04:56:19PM +0530, Viresh Kumar wrote: > Migrate hexagon driver to the new 'set-state' interface provided by > 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. > > We weren't doing anything in the ->set_mode() callback. So, this patch > doesn't provide any set-state callbacks. > > Cc: Richard Kuo > Cc: linux-hexagon@vger.kernel.org > Signed-off-by: Viresh Kumar > --- > arch/hexagon/kernel/time.c | 17 +---------------- > 1 file changed, 1 insertion(+), 16 deletions(-) > Hexagon bits look fine to me, thanks! Acked-by: Richard Kuo -- Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project -- 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/