From: Martin Lorenz <martin@lorenz.eu.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Pavel Machek <pavel@ucw.cz>
Subject: Re: Remove hotplug cpu crap from cpufreq.
Date: Thu, 2 Nov 2006 08:33:53 +0100 [thread overview]
Message-ID: <20061102073353.GH6170@gimli> (raw)
In-Reply-To: <Pine.LNX.4.64.0611011512450.25218@g5.osdl.org>
On Wed, Nov 01, 2006 at 03:21:09PM -0800, Linus Torvalds wrote:
>
>
> On Thu, 2 Nov 2006, Rafael J. Wysocki wrote:
> >
> > Won't there be any problems with suspend on SMP vs cpufreq if this stuff is
> > removed?
>
> Well, at least traditionally, the hotplug locking has caused more problems
> than it has fixed, but at least right _now_ it seems to work.
if I am not completely mistaken I also need this for proper
suspend/resume on my X60s (CoreDUO machine) and THIS is one of
the things that DO work.
gruss
mlo
--
Dipl.-Ing. Martin Lorenz
They that can give up essential liberty
to obtain a little temporary safety
deserve neither liberty nor safety.
Benjamin Franklin
please encrypt your mail to me
GnuPG key-ID: F1AAD37D
get it here:
http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0xF1AAD37D
ICQ UIN: 33588107
next prev parent reply other threads:[~2006-11-02 7:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 22:59 Remove hotplug cpu crap from cpufreq Dave Jones
2006-11-01 23:09 ` Rafael J. Wysocki
2006-11-01 23:21 ` Linus Torvalds
2006-11-02 7:33 ` Martin Lorenz [this message]
2006-11-01 23:09 ` Linus Torvalds
2006-11-01 23:32 ` Dave Jones
2006-11-02 18:46 ` Dipankar Sarma
2006-11-02 0:17 ` Andrew Morton
2006-11-02 4:27 ` Gautham R Shenoy
2006-11-02 19:04 ` Dipankar Sarma
2006-11-02 19:30 ` Linus Torvalds
2006-11-02 21:40 ` Dipankar Sarma
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=20061102073353.GH6170@gimli \
--to=martin@lorenz.eu.org \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=torvalds@osdl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.