cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Laurence Darby <ldarby@tuffmail.com>
To: Thomas Renninger <trenn@suse.de>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: [PATCH] Re: cpufreq limits avilable frequencies to 800MHz on git kernel
Date: Fri, 18 Jul 2008 12:38:58 +0100	[thread overview]
Message-ID: <20080718123858.eb989874.ldarby@tuffmail.com> (raw)
In-Reply-To: <200807181236.16389.trenn@suse.de>

Thomas Renninger wrote:

> On Friday 18 July 2008 12:41:59 pm Laurence Darby wrote:
> >
> > I tried this patch, but I don't think it made a difference, ie. _PPC
> > still got called before the rest.  Was this meant to fix my E8400
> > not being recognised problem?
> 
> Sorry, I not only messed up with mixing up two variables, but also
> with mailing...
> 
> Below  is the one that may work if this really is the problem.
> 

This stops _PPC output appearing altogether, but still gets the same
messages:

...
[    8.168008] acpi-cpufreq: acpi_cpufreq_cpu_init
[    8.168008] cpufreq-core: initialization failed
...

Laurence

  reply	other threads:[~2008-07-18 11:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-23 17:44 cpufreq limits avilable frequencies to 800MHz on git kernel Arkadiusz Miskiewicz
2008-05-24  1:25 ` Andrew Morton
2008-05-25  9:36   ` Arkadiusz Miskiewicz
2008-05-25 15:03     ` Thomas Renninger
2008-05-26  7:07       ` Arkadiusz Miskiewicz
2008-05-26 11:37         ` Thomas Renninger
2008-05-26 16:15           ` Arkadiusz Miskiewicz
2008-05-26 16:23             ` Arkadiusz Miskiewicz
2008-07-17 13:48               ` [PATCH] " Thomas Renninger
2008-07-17 21:40                 ` Andrew Morton
2008-07-18  2:46                   ` Thomas Renninger
2008-07-18 10:41                 ` Laurence Darby
2008-07-18 10:36                   ` Thomas Renninger
2008-07-18 11:38                     ` Laurence Darby [this message]
2008-05-27  9:35             ` Thomas Renninger
2008-05-26 12:28         ` Thomas Renninger

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=20080718123858.eb989874.ldarby@tuffmail.com \
    --to=ldarby@tuffmail.com \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=trenn@suse.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