From: Andrew Morton <akpm@linux-foundation.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Dave Jones <davej@redhat.com>, Dominik Brodowski <linux@brodo.de>,
dave.mueller@gmx.ch, linux-kernel@vger.kernel.org
Subject: Re: Fwd: [Bug 14340] New: speedstep-ich driver not working in 2.6.31
Date: Sun, 18 Oct 2009 20:54:59 -0700 [thread overview]
Message-ID: <20091018205459.f94d89c5.akpm@linux-foundation.org> (raw)
In-Reply-To: <200910191418.23238.rusty@rustcorp.com.au>
On Mon, 19 Oct 2009 14:18:21 +1030 Rusty Russell <rusty@rustcorp.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@gmx.ch, compile-tested only)
>
> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
> To: Dave Jones <davej@redhat.com>
> To: Dominik Brodowski <linux@brodo.de>
> Cc: dave.mueller@gmx.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.
next prev parent reply other threads:[~2009-10-19 3:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091007201108.GA16813@redhat.com>
2009-10-19 3:48 ` Fwd: [Bug 14340] New: speedstep-ich driver not working in 2.6.31 Rusty Russell
2009-10-19 3:54 ` Andrew Morton [this message]
2009-10-19 5:03 ` [PATCH] cpufreq: use an enum for speedstep processor identification Rusty Russell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091018205459.f94d89c5.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dave.mueller@gmx.ch \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
--cc=rusty@rustcorp.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox