From: Dave Jones <davej@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Adrian Bunk <bunk@stusta.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Duncan <1i5t5.duncan@cox.net>, Neil Brown <neilb@suse.de>,
mingo@redhat.com, linux-raid@vger.kernel.org,
cpufreq@lists.linux.org.uk, lenb@kernel.org,
linux-acpi@vger.kernel.org, Jan Altenberg <jan@linutronix.de>,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org,
Andrew Clayton <andrew@digital-domain.net>,
Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: 2.6.20-rc6: known regressions with patches
Date: Mon, 29 Jan 2007 07:58:55 -0500 [thread overview]
Message-ID: <20070129125855.GA30599@redhat.com> (raw)
In-Reply-To: <20070129084548.GA10578@elte.hu>
On Mon, Jan 29, 2007 at 09:45:48AM +0100, Ingo Molnar wrote:
>
> * Adrian Bunk <bunk@stusta.de> wrote:
>
> > Subject : ACPI: fix cpufreq regression
> > References : http://lkml.org/lkml/2007/1/16/120
> > Submitter : Ingo Molnar <mingo@elte.hu>
> > Caused-By : Dave Jones <davej@redhat.com>
> > commit 0916bd3ebb7cefdd0f432e8491abe24f4b5a101e
> > Handled-By : Ingo Molnar <mingo@elte.hu>
> > Patch : http://lkml.org/lkml/2007/1/16/120
> > Status : patch available
>
> this is commit e4233dec749a3519069d9390561b5636a75c7579 meanwhile.
Thanks for pushing this on in my absense btw.
FWIW, it has my belated ACK :)
I've asked for it to be in 19.3 too as the same bug exists there.
Dave
--
http://www.codemonkey.org.uk
prev parent reply other threads:[~2007-01-29 12:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0701241847360.25027@woody.linux-foundation.org>
2007-01-26 18:18 ` 2.6.20-rc6: known regressions with patches Adrian Bunk
2007-01-29 8:45 ` Ingo Molnar
2007-01-29 12:58 ` Dave Jones [this message]
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=20070129125855.GA30599@redhat.com \
--to=davej@redhat.com \
--cc=1i5t5.duncan@cox.net \
--cc=akpm@osdl.org \
--cc=andrew@digital-domain.net \
--cc=bunk@stusta.de \
--cc=cpufreq@lists.linux.org.uk \
--cc=jan@linutronix.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-raid@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=neilb@suse.de \
--cc=ralf@linux-mips.org \
--cc=torvalds@linux-foundation.org \
--cc=trond.myklebust@fys.uio.no \
/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;
as well as URLs for NNTP newsgroup(s).