From: Tejun Heo <tj@kernel.org>
To: Christoph Lameter <cl@linux.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Pekka Enberg <penberg@kernel.org>
Subject: Re: [PATCH tip:x86/mm 3/3] acpi throttling: Use this_cpu_has and simplify code current cpu
Date: Wed, 30 Mar 2011 17:19:48 +0200 [thread overview]
Message-ID: <20110330151948.GI17523@htj.dyndns.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1103300918240.25965@router.home>
On Wed, Mar 30, 2011 at 09:20:08AM -0500, Christoph Lameter wrote:
> > Ingo, are you planning on picking these up?
>
> Guess the patches missed the merge period. There could be more
> optimizations of arch code if the infrastructure for this_cpu_has() would
> be in but I guess I better hold off for awhile.
Yeah, merging didn't go very smooth with your recent patches. Sorry
about that. I applied the this_cpu_has() patches to x86-mm and will
soon send pull request to Ingo. Please feel free to send further
patches on top of that tree.
git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git
Thanks.
--
tejun
next prev parent reply other threads:[~2011-03-30 15:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-12 11:50 [PATCH tip:x86/mm 1/3] x86: A fast way to check capabilities of the " Tejun Heo
2011-03-12 11:50 ` [PATCH tip:x86/mm 2/3] x86: Use this_cpu_has for thermal_interrupt " Tejun Heo
2011-03-12 11:51 ` [PATCH tip:x86/mm 3/3] acpi throttling: Use this_cpu_has and simplify code " Tejun Heo
2011-03-28 16:40 ` Tejun Heo
2011-03-30 14:20 ` Christoph Lameter
2011-03-30 15:19 ` Tejun Heo [this message]
2011-03-14 19:49 ` [PATCH tip:x86/mm 1/3] x86: A fast way to check capabilities of the " Andi Kleen
2011-03-30 15:58 ` H. Peter Anvin
2011-03-30 16:07 ` Tejun Heo
2011-03-30 16:15 ` Christoph Lameter
2011-03-30 16:16 ` H. Peter Anvin
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=20110330151948.GI17523@htj.dyndns.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®