All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Sweetman <safemode2@comcast.net>
To: Daniel Drake <dsd@gentoo.org>
Cc: Joshua Hoblitt <jhoblitt@ifa.hawaii.edu>,
	davej@redhat.com, duaneg@dghda.com, prakash@punnoor.de,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powernow-k8: depend on acpi-processor for SMP systems
Date: Wed, 16 May 2007 21:03:55 -0400	[thread overview]
Message-ID: <464BA9FB.9020102@comcast.net> (raw)
In-Reply-To: <464BA7C2.5040504@gentoo.org>

Daniel Drake wrote:
> Joshua Hoblitt wrote:
>> I don't think this is quiet right either as Ed Sweetman has reported
>> that this issue doesn't occur on single socket/multi-core systems.
>
> Where did he write that? In an off-list mail, Ed seemed to agree with 
> my patch.
>
> Daniel
>
>
What i didn't agree with was the dependency on the acpi P-state driver 
for single socket multi-core systems, where in the original post of this 
thread, Joshua was stating that smp systems required that driver.   
Later it was found that the acpi p-state driver was only being used to 
enforce the dependency on the acpi_processor driver ...which is the 
actual driver we care about (dependency wise).  

So yes, I do agree with your patch, in so far as my experience with the 
hardware.



  reply	other threads:[~2007-05-17  1:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-16 23:50 [PATCH] powernow-k8: depend on acpi-processor for SMP systems Daniel Drake
2007-05-17  0:03 ` Dave Jones
2007-05-17  0:26 ` Joshua Hoblitt
2007-05-17  0:37   ` Dave Jones
2007-05-17  0:54   ` Daniel Drake
2007-05-17  1:03     ` Ed Sweetman [this message]
2007-05-17  9:02 ` Pavel Machek
2007-05-17 10:24   ` Ed Sweetman
2007-06-04 10:52     ` Pavel Machek
2007-05-17 18:13 ` Len Brown
2007-05-17 18:23   ` Dave Jones
2007-05-17 21:29     ` Ed Sweetman
2007-05-17 21:40       ` Ed Sweetman
2007-05-17 21:52         ` Dave Jones
2007-05-17 22:15           ` Ed Sweetman
2007-05-17 21:43       ` 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=464BA9FB.9020102@comcast.net \
    --to=safemode2@comcast.net \
    --cc=davej@redhat.com \
    --cc=dsd@gentoo.org \
    --cc=duaneg@dghda.com \
    --cc=jhoblitt@ifa.hawaii.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prakash@punnoor.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 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.