linux-kernel - Re: [PATCH v2] powercap, intel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1869286.F6FKdkBDy4@vostro.rjw.lan>
Date:	Thu, 10 Dec 2015 01:52:37 +0100
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Jacob Pan <jacob.jun.pan@...ux.intel.com>
Cc:	Prarit Bhargava <prarit@...hat.com>, linux-kernel@...r.kernel.org,
	"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
	Radivoje Jovanovic <radivoje.jovanovic@...el.com>,
	Seiichi Ikarashi <s.ikarashi@...fujitsu.com>,
	Mathias Krause <minipli@...glemail.com>,
	Ajay Thomas <ajay.thomas.david.rajamanickam@...el.com>
Subject: Re: [PATCH v2] powercap, intel_rapl.c, fix BIOS lock check

On Wednesday, December 09, 2015 03:31:23 PM Jacob Pan wrote:
> On Thu, 10 Dec 2015 00:38:27 +0100
> "Rafael J. Wysocki" <rjw@...ysocki.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.

So which "stable" series in particular should it go to?  All applicable?

Thanks,
Rafael

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/