cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ashley Pittman <ashley@pittman.co.uk>
To: Dominik Brodowski <linux@brodo.de>
Cc: davej@codemonkey.org.uk, cpufreq <cpufreq@www.linux.org.uk>
Subject: Re: TODO list, patches will follow...
Date: Thu, 20 Nov 2003 11:27:44 +0000	[thread overview]
Message-ID: <1069327664.26133.1326.camel@ashley> (raw)
In-Reply-To: <20031119182928.GA20576@brodo.de>

On Wed, 2003-11-19 at 18:29, Dominik Brodowski wrote:
> Here are a few TODO items I'm aware of for cpufreq in 2.6.

Could one of you take a look at the problem I reported with the current
longhaul driver and my chipset?  My machine locks solid with current
kernels.

I would post a link to the archive but I've misplaced my list password,
I posted a patch which prevents the lockup to the list with the subject
"Patch to stop i386 longhaul from deadlocking the kernel" recently.

Ashley,

      reply	other threads:[~2003-11-20 11:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-19 18:29 TODO list, patches will follow Dominik Brodowski
2003-11-20 11:27 ` Ashley Pittman [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=1069327664.26133.1326.camel@ashley \
    --to=ashley@pittman.co.uk \
    --cc=cpufreq@www.linux.org.uk \
    --cc=davej@codemonkey.org.uk \
    --cc=linux@brodo.de \
    /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