From: Len Brown <lenb@kernel.org>
To: akpm@linux-foundation.org
Cc: linux-acpi@vger.kernel.org, davej@redhat.com, efault@gmx.de,
jaswinder@kernel.org, len.brown@intel.com, mingo@elte.hu,
rusty@rustcorp.com.au, tglx@linutronix.de,
venkatesh.pallipadi@intel.com, yakui.zhao@intel.com,
yanmin_zhang@linux.intel.com
Subject: Re: [patch 1/9] arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c: avoid cross-CPU interrupts by using smp_call_function_any()
Date: Tue, 22 Dec 2009 15:14:11 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0912221514080.5153@localhost.localdomain> (raw)
In-Reply-To: <200912220019.nBM0Jwbq004738@imap1.linux-foundation.org>
applied
thanks,
Len Brown, Intel Open Source Technology Center
prev parent reply other threads:[~2009-12-22 20:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 0:19 [patch 1/9] arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c: avoid cross-CPU interrupts by using smp_call_function_any() akpm
2009-12-22 20:14 ` 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.0912221514080.5153@localhost.localdomain \
--to=lenb@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=efault@gmx.de \
--cc=jaswinder@kernel.org \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.com \
--cc=yakui.zhao@intel.com \
--cc=yanmin_zhang@linux.intel.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