cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: [PATCH] redirect speedstep-centrino maintainer mail to cpufreq list
Date: Wed, 21 Jun 2006 16:37:26 -0400	[thread overview]
Message-ID: <20060621203726.GA7620@redhat.com> (raw)
In-Reply-To: <4499A8F4.6020101@goop.org>

On Wed, Jun 21, 2006 at 01:15:48PM -0700, Jeremy Fitzhardinge wrote:
 > I haven't really maintained this driver for a while, and I'm not
 > keeping up with the latest in Intel power management.  I get a steady
 > stream of mail which I don't really do anything useful with; the
 > cpufreq list seems like a better destination, unless someone wants to
 > get the mail directly.

Heh, I actually had meant to ask you about this.
I'll apply this for .18

Thanks,

		Dave

-- 
http://www.codemonkey.org.uk

      reply	other threads:[~2006-06-21 20:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-21 20:15 [PATCH] redirect speedstep-centrino maintainer mail to cpufreq list Jeremy Fitzhardinge
2006-06-21 20:37 ` 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=20060621203726.GA7620@redhat.com \
    --to=davej@redhat.com \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=jeremy@goop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox