From: Dave Jones <davej@redhat.com>
To: Jan Killius <jkillius@arcor.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops with cpufreq on 2.6.5-mm1
Date: Tue, 6 Apr 2004 14:54:41 +0100 [thread overview]
Message-ID: <20040406135441.GC32405@redhat.com> (raw)
In-Reply-To: <20040406101609.GA25248@gate.unimatrix>
On Tue, Apr 06, 2004 at 12:16:09PM +0200, Jan Killius wrote:
> The patch have fixed the problem. thx
Can you try out the fully merged patch at
http://www.codemonkey.org.uk/projects/bitkeeper/cpufreq
too please ?
Dave
next prev parent reply other threads:[~2004-04-06 13:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-06 10:16 Oops with cpufreq on 2.6.5-mm1 Jan Killius
2004-04-06 13:54 ` Dave Jones [this message]
2004-04-06 14:53 ` Jan Killius
2004-04-06 15:03 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2004-04-07 0:26 Jan Killius
2004-04-06 8:45 Jan Killius
2004-04-06 0:05 Jan Killius
2004-04-06 9:51 ` Angelo Dell'Aera
2004-04-06 10:49 ` Dave Jones
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=20040406135441.GC32405@redhat.com \
--to=davej@redhat.com \
--cc=jkillius@arcor.de \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.