public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: Arkadiusz Miskiewicz <arekm@maven.pl>
Cc: linux-kernel@vger.kernel.org, cpufreq@lists.linux.org.uk,
	Andrew Morton <akpm@linux-foundation.org>,
	gnorton@novell.com, miguel@novell.com
Subject: Re: cpufreq limits avilable frequencies to 800MHz on git kernel
Date: Mon, 26 May 2008 14:28:38 +0200	[thread overview]
Message-ID: <1211804918.29901.187.camel@queen.suse.de> (raw)
In-Reply-To: <200805260907.05561.arekm@maven.pl>

...
> > Sounds related to:
> > [Bug 374099] T61p speedstep problems (ondemand scheduler)
> > https://bugzilla.novell.com/show_bug.cgi?id=374099
> 
> login/pass protected
Sorry, OpenSUSE bugs should by default be public, no idea why this one
was not.
Should be public now.
Readable for the public, you can post if you get an bugzilla.novell.com
account.

Thanks,

    Thomas


      parent reply	other threads:[~2008-05-26 12:34 UTC|newest]

Thread overview: 13+ 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-05-27  9:35             ` Thomas Renninger
2008-05-26 12:28         ` Thomas Renninger [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=1211804918.29901.187.camel@queen.suse.de \
    --to=trenn@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=arekm@maven.pl \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=gnorton@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miguel@novell.com \
    /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