From: Len Brown <lenb@kernel.org>
To: Alex Chiang <achiang@hp.com>
Cc: shemminger@linux-foundation.org, ming.m.lin@intel.com,
linux-acpi@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ACPI: processor: only call _PDC on physically present processors
Date: Tue, 19 Jan 2010 23:42:29 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.1001192340140.4265@localhost.localdomain> (raw)
In-Reply-To: <20100114201214.GH4545@ldl.fc.hp.com>
A couple reasons to not get excited about this solution.
I don't like the processor enumeration code moving to a file called
processor_pdc.c.
Too big for rc4 -- a logical revert to evaluate PDC when
we did in 2.6.32 would be more attractive at this point.
thanks,
Len Brown, Intel Open Source Technology Center
prev parent reply other threads:[~2010-01-20 4:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 20:12 [PATCH] ACPI: processor: only call _PDC on physically present processors Alex Chiang
2010-01-20 4:42 ` Len Brown [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=alpine.LFD.2.00.1001192340140.4265@localhost.localdomain \
--to=lenb@kernel.org \
--cc=achiang@hp.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=shemminger@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox