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 S1753446AbbLIXcU (ORCPT <rfc822;w@1wt.eu>);
	Wed, 9 Dec 2015 18:32:20 -0500
Received: from mga14.intel.com ([192.55.52.115]:49306 "EHLO mga14.intel.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751937AbbLIXcT (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Wed, 9 Dec 2015 18:32:19 -0500
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.20,405,1444719600"; 
   d="scan'208";a="838027870"
Date: Wed, 9 Dec 2015 15:31:23 -0800
From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Prarit Bhargava <prarit@redhat.com>, linux-kernel@vger.kernel.org,
        "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
        Radivoje Jovanovic <radivoje.jovanovic@intel.com>,
        Seiichi Ikarashi <s.ikarashi@jp.fujitsu.com>,
        Mathias Krause <minipli@googlemail.com>,
        Ajay Thomas <ajay.thomas.david.rajamanickam@intel.com>,
        jacob.jun.pan@linux.intel.com
Subject: Re: [PATCH v2] powercap, intel_rapl.c, fix BIOS lock check
Message-ID: <20151209153123.60220026@icelake>
In-Reply-To: <5563622.j8xTDST9Ds@vostro.rjw.lan>
References: <1449667872-11197-1-git-send-email-prarit@redhat.com>
	<20151209085355.6442a508@icelake>
	<5563622.j8xTDST9Ds@vostro.rjw.lan>
Organization: OTC
X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.23; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, 10 Dec 2015 00:38:27 +0100
"Rafael J. Wysocki" <rjw@rjwysocki.net> wrote:

> OK, I've put it into my bleeding-edge branch as 4.5 candidate, but do
> we want it in "stable" and therefore should it be pushed for 4.4?
yes, it is a bug fix that may affect many systems locked by BIOS.