linux-kernel - Re: Fwd: [Bug 14340] New: speedstep-ich driver not working in 2.6.31

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: <20091018205459.f94d89c5.akpm@linux-foundation.org>
Date:	Sun, 18 Oct 2009 20:54:59 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Rusty Russell <rusty@...tcorp.com.au>
Cc:	Dave Jones <davej@...hat.com>, Dominik Brodowski <linux@...do.de>,
	dave.mueller@....ch, linux-kernel@...r.kernel.org
Subject: Re: Fwd: [Bug 14340] New: speedstep-ich driver not working in
 2.6.31

On Mon, 19 Oct 2009 14:18:21 +1030 Rusty Russell <rusty@...tcorp.com.au> wrote:

> Subject: speedstep-ich: fix error caused by 394122ab144dae4b276d74644a2f11c44a60ac5c
> 
> "[CPUFREQ] cpumask: avoid playing with cpus_allowed in speedstep-ich.c"
> changed the code to mistakenly pass the current cpu as the "processor"
> argument of speedstep_get_frequency(), whereas it should be the type of
> the processor.
> 
> (Based on patch by dave.mueller@....ch, compile-tested only)
> 
> Signed-off-by: Rusty Russell <rusty@...tcorp.com.au>
> To: Dave Jones <davej@...hat.com>
> To: Dominik Brodowski <linux@...do.de>
> Cc: dave.mueller@....ch

administriviata:

- Please include the full URL to the bugzilla report in the changelog
  when fixing bugzilla reports.  To make it easy and reliable for people
  who troll the commits closing off reports.  I use the format:

	Addresses http://bugzilla.kernel.org/show_bug.cgi?id=14340

- Please give the reporter a "Reported-by:".  And a beer.

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