cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "Rafał Bilski" <rafalbilski@interia.pl>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: [PATCH] Longhaul - Disable arbiter CLE266
Date: Wed, 27 Sep 2006 01:06:39 -0400	[thread overview]
Message-ID: <20060927050639.GC3571@redhat.com> (raw)
In-Reply-To: <45198341.4080202@interia.pl>

On Tue, Sep 26, 2006 at 09:45:05PM +0200, Rafał Bilski wrote:
 > Please ignore previous two messages. :-)
 > 
 > This patch is adding support for CPU connected to CLE266 
 > chipset. For older CPU this is only way. For "Powersaver" 
 > processor this way will be used if ACPI C3 isn't supported.
 > 
 > Signed-off-by: Rafał Bilski <rafalbilski@interia.pl>
 
Argh, I already applied the second of the earlier diffs.
Can you send an incremental diff to whats in cpufreq.git?

Thanks,

	Dave 

  reply	other threads:[~2006-09-27  5:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-26 19:45 [PATCH] Longhaul - Disable arbiter CLE266 Rafał Bilski
2006-09-27  5:06 ` Dave Jones [this message]
2006-09-27  6:25   ` Rafał Bilski
  -- strict thread matches above, loose matches on Subject: below --
2006-09-24 18:28 Rafał Bilski
2006-09-23  5:59 Rafał Bilski

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=20060927050639.GC3571@redhat.com \
    --to=davej@redhat.com \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=rafalbilski@interia.pl \
    /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