From: Christoph Lameter <cl@linux.com>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Tony Luck <tony.luck@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>
Subject: Re: Final per cpu consistency patch for -next or late in 3.19 merge period
Date: Tue, 2 Dec 2014 11:33:15 -0600 (CST) [thread overview]
Message-ID: <alpine.DEB.2.11.1412021131350.19228@gentwo.org> (raw)
In-Reply-To: <20141202171102.GC10918@htj.dyndns.org>
On Tue, 2 Dec 2014, Tejun Heo wrote:
> Sure, I just wanna make sure we don't have dangling references to
> __get_cpu_var() which no longer exists. There are also a couple
> places where comment text refers to it. Let's please take care of
> them too.
Here is the ia64 patch:
From: Christoph Lameter <cl@linux.com>
Subject: ia64: Update comment that references __get_cpu_var
__get_cpu_var was removed. Update the comments.
Cc: Tony Luck <tony.luck@intel.com>
Cc: Fenghua Yu <fenghua.yu@intel.com>
Signed-off-by: Christoph Lameter <cl@linux.com>
Index: linux/arch/ia64/include/asm/percpu.h
===================================================================
--- linux.orig/arch/ia64/include/asm/percpu.h
+++ linux/arch/ia64/include/asm/percpu.h
@@ -35,8 +35,8 @@ extern void *per_cpu_init(void);
/*
* Be extremely careful when taking the address of this variable! Due to virtual
- * remapping, it is different from the canonical address returned by __get_cpu_var(var)!
- * On the positive side, using __ia64_per_cpu_var() instead of __get_cpu_var() is slightly
+ * remapping, it is different from the canonical address returned by this_cpu_ptr(&var)!
+ * On the positive side, using __ia64_per_cpu_var() instead of this_cpu_ptr() is slightly
* more efficient.
*/
#define __ia64_per_cpu_var(var) (*({ \
next prev parent reply other threads:[~2014-12-02 17:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 18:31 Christoph Lameter
2014-12-02 16:40 ` Tejun Heo
2014-12-02 16:57 ` Christoph Lameter
2014-12-02 17:11 ` Tejun Heo
2014-12-02 17:32 ` Mathieu Desnoyers
2014-12-02 17:51 ` Christoph Lameter
2014-12-02 17:33 ` Christoph Lameter [this message]
2014-12-02 19:27 ` Luck, Tony
2014-12-02 17:34 ` Christoph Lameter
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.DEB.2.11.1412021131350.19228@gentwo.org \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=fenghua.yu@intel.com \
--cc=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@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
all inboxes | Powered by JetHome®