From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752091AbcL3Rws (ORCPT ); Fri, 30 Dec 2016 12:52:48 -0500 Received: from mga09.intel.com ([134.134.136.24]:1412 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751280AbcL3Rwr (ORCPT ); Fri, 30 Dec 2016 12:52:47 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,432,1477983600"; d="scan'208";a="48669933" Message-ID: <1483120143.27585.83.camel@linux.intel.com> Subject: Re: [PATCH 0/3] cpufreq: intel_pstate: Locking and limits fix-ups From: Srinivas Pandruvada To: "Rafael J. Wysocki" , Linux PM Cc: LKML Date: Fri, 30 Dec 2016 09:49:03 -0800 In-Reply-To: <5344750.TOCWYON8QY@aspire.rjw.lan> References: <5344750.TOCWYON8QY@aspire.rjw.lan> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.18.5.2 (3.18.5.2-1.fc23) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2016-12-30 at 15:54 +0100, Rafael J. Wysocki wrote: > Hi, > > This series fixes a couple of possible locking issues and limits > synchronization > in intel pstate. > > [1/3] Add locking to intel_pstate_resume(). > [2/3] Add locking to intel_cpufreq_verify_policy(). > [3/3] Always keep all limits settings in sync. > Looks good to me. Acked-by: Srinivas Pandruvada Thanks, Srinivas