From: Dave Jones <davej@redhat.com>
To: "Rafał Bilski" <rafalbilski@interia.pl>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: [PATCH] Longhaul - Use hardware support
Date: Thu, 6 Jul 2006 15:48:40 -0400 [thread overview]
Message-ID: <20060706194840.GO13168@redhat.com> (raw)
In-Reply-To: <44A8A8C9.3070901@interia.pl>
On Mon, Jul 03, 2006 at 07:19:05AM +0200, Rafał Bilski wrote:
> This patch depends on "Longhaul - There are limits".
> Minimal change necessary for hardware support.
>
> Changes in longhaul.c:
> - most important - now C3 state is causing transition,
> - code resopnsible for clearing "bus master" bit removed,
> - protect bcr2 transition in the same way as longhaul.
>
> Signed-off-by: Rafał Bilski <rafalbilski@interia.pl>
applied, thanks.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-07-06 19:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-03 5:19 [PATCH] Longhaul - Use hardware support Rafał Bilski
2006-07-06 19:48 ` Dave Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-02 20:51 Rafał Bilski
2006-07-02 21:02 ` 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=20060706194840.GO13168@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