From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1754431AbcL3PC5 (ORCPT <rfc822;w@1wt.eu>);
        Fri, 30 Dec 2016 10:02:57 -0500
Received: from cloudserver094114.home.net.pl ([79.96.170.134]:46197 "EHLO
        cloudserver094114.home.net.pl" rhost-flags-OK-OK-OK-OK)
        by vger.kernel.org with ESMTP id S1754317AbcL3PCz (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 30 Dec 2016 10:02:55 -0500
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux PM <linux-pm@vger.kernel.org>,
        Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] cpufreq: intel_pstate: Locking and limits fix-ups
Date: Fri, 30 Dec 2016 15:54:30 +0100
Message-ID: <5344750.TOCWYON8QY@aspire.rjw.lan>
User-Agent: KMail/4.14.10 (Linux/4.10.0-rc1+; KDE/4.14.9; x86_64; ; )
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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.

Thanks,
Rafael