From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from mail.linuxfoundation.org ([140.211.169.12]:47658 "EHLO
        mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751749AbdJ3LUr (ORCPT
        <rfc822;stable@vger.kernel.org>); Mon, 30 Oct 2017 07:20:47 -0400
Date: Mon, 30 Oct 2017 12:20:59 +0100
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Stable kernel maintainers <stable@vger.kernel.org>
Subject: Re: [Urgent] Do not include commit 0cc2b4e5a020 into -stable yet
Message-ID: <20171030112059.GA10987@kroah.com>
References: <1794473.anWR3RpfPz@aspire.rjw.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1794473.anWR3RpfPz@aspire.rjw.lan>
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

On Mon, Oct 30, 2017 at 11:57:54AM +0100, Rafael J. Wysocki wrote:
> Hi Greg at al,
> 
> The following commit:
> 
> commit 0cc2b4e5a020fc7f4d1795741c116c983e9467d7
> Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Date:   Tue Oct 24 15:20:45 2017 +0200
> 
>     PM / QoS: Fix device resume latency PM QoS
> 
> was marked for -stable inclusion, but unfortunately there's a bug in it, so
> please don't include it just yet.
> 
> There is a fix for this in my linux-next branch, but I first need to make
> sure that the fix gets to Linus before it can go into -stable.

Thanks for letting me know, now dropped from the 4.13-stable queue.

greg k-h