From: Christoph Lameter <cl@linux.com>
To: Tejun Heo <tj@kernel.org>
Cc: akpm@linuxfoundation.org, linux-kernel@vger.kernel.org,
Tony Luck <tony.luck@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>
Subject: [PATCH 3/4] ia64: Update comment that references __get_cpu_var
Date: Tue, 02 Dec 2014 15:24:32 -0600 [thread overview]
Message-ID: <20141202212439.918330465@linux.com> (raw)
In-Reply-To: 20141202212429.996456533@linux.com
[-- Attachment #1: ia64_update --]
[-- Type: text/plain, Size: 944 bytes --]
__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 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 21:24 [PATCH 0/4] percpu: Consistent per cpu operations: The final edition Christoph Lameter
2014-12-02 21:24 ` [PATCH 1/4] Remove __get_cpu_var and __raw_get_cpu_var macros Christoph Lameter
2014-12-02 21:24 ` [PATCH 2/4] Update local_ops.txt to reflect this_cpu operations Christoph Lameter
2014-12-02 21:24 ` Christoph Lameter [this message]
2014-12-02 21:24 ` [PATCH 4/4] parisc: Update comments refereing to __get_cpu_var 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=20141202212439.918330465@linux.com \
--to=cl@linux.com \
--cc=akpm@linuxfoundation.org \
--cc=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.