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 S1751422AbdCBXea (ORCPT <rfc822;w@1wt.eu>);
        Thu, 2 Mar 2017 18:34:30 -0500
Received: from cloudserver094114.home.net.pl ([79.96.170.134]:54438 "EHLO
        cloudserver094114.home.net.pl" rhost-flags-OK-OK-OK-OK)
        by vger.kernel.org with ESMTP id S1750709AbdCBXe3 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 2 Mar 2017 18:34:29 -0500
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux PM <linux-pm@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
        Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: [PATCH 0/3] cpufreq: intel_pstate: Fixes related to the passive mode
Date: Thu, 02 Mar 2017 23:20:20 +0100
Message-ID: <1573986.gdsgdO0VUn@aspire.rjw.lan>
User-Agent: KMail/4.14.10 (Linux/4.10.0+; 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 some passive mode behavior related to limits and the
cpu_frequency tracepoint.

It depends on https://patchwork.kernel.org/patch/9594447/ (which is in
linux-next already), but it doesn't depend on the other series I posted
yesterday (https://patchwork.kernel.org/patch/9597147/ ,
https://patchwork.kernel.org/patch/9597145/,
https://patchwork.kernel.org/patch/9597137/).

All three patches in this series are reasonably straightforward and should
not be controversial.  Also they should affect the passive mode only.

Thanks,
Rafael