linux-kernel - Re: [PATCH 0/5] updates for 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]

Date:	Thu, 08 May 2014 14:08:30 -0700
From:	Dirk Brandewie <dirk.brandewie@...il.com>
To:	"Rafael J. Wysocki" <rjw@...ysocki.net>
CC:	dirk.brandewie@...il.com, linux-kernel@...r.kernel.org,
	linux-pm@...r.kernel.org,
	Dirk Brandewie <dirk.j.brandewie@...el.com>
Subject: Re: [PATCH 0/5] updates for intel_pstate

On 05/08/2014 01:30 PM, Rafael J. Wysocki wrote:
> On Thursday, May 08, 2014 12:57:22 PM dirk.brandewie@...il.com wrote:
>> From: Dirk Brandewie <dirk.j.brandewie@...el.com>
>>
>> Patches 1-4 are bugfixes.  Patch 4 specifically removes the wreckage
>> caused by C0 tracking change.
>
> I would appreciate sending such stuff before the -rc4 time frame.

Agreed.

Patch 1 is a resend the others were sent as soon as they were ready/tested

>
>> Patch 5 Adds new CPU IDs for the Broadwell processors.
>>
>> Dirk Brandewie (5):
>>    intel_pstate: Set turbo VID for Baytrail
>>    intel_pstate: remove setting P state to MAX on init
>>    intel_pstate: Fix fixed point rounding macro
>>    intel_pstate: Remove C0 tracking
>>    intel_pstate: Add CPU IDs for Broadwell processors
>>
>>   drivers/cpufreq/intel_pstate.c | 52 +++++++++++++++++-------------------------
>>   1 file changed, 21 insertions(+), 31 deletions(-)
>
> I'll queue them up for 3.15-rc6, but that's a bit too late.
>
> Next time I may just wait for the next merge window, fixes or not.

OK the reporters of the issues already have the fixes in hand.

>
>

--
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/