From: ian.soboroff@nist.gov
To: lkml@brodo.de
Cc: linux-kernel@vger.kernel.org, davej@suse.de
Subject: Re: 2.6.0-test1 - cpu_freg sysfs nodes?
Date: Tue, 15 Jul 2003 16:50:19 -0400 [thread overview]
Message-ID: <m3n0ffbjlg.fsf@euphrates.ncsl.nist.gov> (raw)
In-Reply-To: <20030715175010.CE2428275@voodoo.strato-webmail.de> (lkml@brodo.de's message of "Tue, 15 Jul 2003 19:50:10 +0200 (CEST)")
lkml@brodo.de writes:
> There is a problem with the proper detection of longrun CPUs, see this
> patch please [davej: can you appply this to your tree, too, please?]
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=105797182628099&w=2
>
> Dominik
This patch solves it for me. Now I have all the cpufreq nodes in
sysfs, and the old /proc interface works as well (meaning I don't have
to rewrite /etc/sysconfig/apm-scripts/apmcontinue ;-)
Thanks!
Ian
next prev parent reply other threads:[~2003-07-15 19:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 17:50 2.6.0-test1 - cpu_freg sysfs nodes? lkml
2003-07-15 20:50 ` ian.soboroff [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-15 17:12 ian.soboroff
2003-07-15 16:42 ` Mattia Dongili
2003-07-15 18:17 ` ian.soboroff
2003-07-15 17:48 ` 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=m3n0ffbjlg.fsf@euphrates.ncsl.nist.gov \
--to=ian.soboroff@nist.gov \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@brodo.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;
as well as URLs for NNTP newsgroup(s).