From: "H. Peter Anvin" <hpa@zytor.com>
To: Tejun Heo <tj@kernel.org>
Cc: Christoph Lameter <cl@linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] x86: Use this_cpu_ops to optimize code
Date: Mon, 20 Dec 2010 17:33:52 -0800 [thread overview]
Message-ID: <4D100400.7060104@zytor.com> (raw)
In-Reply-To: <4D0CD337.4080407@kernel.org>
On 12/18/2010 07:28 AM, Tejun Heo wrote:
> Peter, these three patches are the x86 ones which were in
> percpu#for-next but should go through x86 tree. These should be
> applied on top of percpu#this_cpu_ops.
Does that mean the latter is now a stable base that I can pull into -tip?
-hpa
next prev parent reply other threads:[~2010-12-21 1:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-18 15:28 [PATCH 1/3] x86: Use this_cpu_ops to optimize code Tejun Heo
2010-12-18 15:30 ` [PATCH 2/3] x86: Replace uses of current_cpu_data with this_cpu ops Tejun Heo
2010-12-18 15:30 ` [PATCH 3/3] x86: Use this_cpu_inc_return for nmi counter Tejun Heo
2010-12-21 1:33 ` H. Peter Anvin [this message]
2010-12-21 11:22 ` [PATCH 1/3] x86: Use this_cpu_ops to optimize code Tejun Heo
2010-12-29 21:30 ` H. Peter Anvin
2010-12-30 11:23 ` Tejun Heo
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=4D100400.7060104@zytor.com \
--to=hpa@zytor.com \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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