From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964993AbbLHNzY (ORCPT ); Tue, 8 Dec 2015 08:55:24 -0500 Received: from mail-pf0-f178.google.com ([209.85.192.178]:36772 "EHLO mail-pf0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932675AbbLHNzW (ORCPT ); Tue, 8 Dec 2015 08:55:22 -0500 Date: Tue, 8 Dec 2015 19:25:18 +0530 From: Viresh Kumar To: "Rafael J. Wysocki" Cc: linux-pm@vger.kernel.org, linaro-kernel@lists.linaro.org, ashwin.chaugule@linaro.org, "Rafael J. Wysocki" , LKML Subject: Re: [PATCH][experimantal] cpufreq: governor: Use an atomic variable for synchronization Message-ID: <20151208135518.GE3692@ubuntu> References: <5461074.Yz9lhOaAu0@vostro.rjw.lan> <20151208133633.GC3692@ubuntu> <10138182.WjU9yqx6Gs@vostro.rjw.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <10138182.WjU9yqx6Gs@vostro.rjw.lan> 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 On 08-12-15, 15:19, Rafael J. Wysocki wrote: > We know what should be done. We need to wait for the timer function to > complete, then cancel the work item spawned by it (if any) and then > cancel the timers set by that work item. Yeah, there is no race, but it looks ugly to me. I have written it earlier, and then the spinlock thing looked better to me. :) -- viresh