cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Krisztian Mark Szentes <office@lsa.at>
Cc: Segher Boessenkool <segher@koffie.nl>,
	"debian-powerpc@lists.debian.org"
	<debian-powerpc@lists.debian.org>,
	cpufreq@www.linux.org.uk
Subject: Re: cpufreq on TiBook 400 MHz
Date: Wed, 09 Jun 2004 11:46:55 -0500	[thread overview]
Message-ID: <1086798535.1981.12.camel@gaston> (raw)
In-Reply-To: <200406091247.51210.office@lsa.at>


> Has it convinced you to include the Titanium 400 MHz into the future 
> cpufreq supported models?

Your numbers look good. Send me a patch :)

Ben.

      reply	other threads:[~2004-06-09 16:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200305211853.54638.office@lsa.at>
     [not found] ` <200306121600.06552.office@lsa.at>
     [not found]   ` <1055685144.608.0.camel@gaston>
2004-06-09 10:47     ` cpufreq on TiBook 400 MHz Krisztian Mark Szentes
2004-06-09 16:46       ` Benjamin Herrenschmidt [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=1086798535.1981.12.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=cpufreq@www.linux.org.uk \
    --cc=debian-powerpc@lists.debian.org \
    --cc=office@lsa.at \
    --cc=segher@koffie.nl \
    /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