From: Christoph Lameter <cl@linux.com>
To: Tejun Heo <tj@kernel.org>
Cc: akpm@linuxfoundation.org, linux-kernel@vger.kernel.org,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>
Subject: [PATCH 4/4] parisc: Update comments refereing to __get_cpu_var
Date: Tue, 02 Dec 2014 15:24:33 -0600 [thread overview]
Message-ID: <20141202212440.031271472@linux.com> (raw)
In-Reply-To: 20141202212429.996456533@linux.com
[-- Attachment #1: parisc_update --]
[-- Type: text/plain, Size: 869 bytes --]
__get_cpu_var was removed. Update comments to refer to
this_cpu_ptr() instead.
Cc: "James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>
Signed-off-by: Christoph Lameter <cl@linux.com>
Index: linux/arch/parisc/lib/fixup.S
===================================================================
--- linux.orig/arch/parisc/lib/fixup.S
+++ linux/arch/parisc/lib/fixup.S
@@ -38,14 +38,14 @@
LDREGX \t2(\t1),\t2
addil LT%exception_data,%r27
LDREG RT%exception_data(%r1),\t1
- /* t1 = &__get_cpu_var(exception_data) */
+ /* t1 = this_cpu_ptr(&exception_data) */
add,l \t1,\t2,\t1
/* t1 = t1->fault_ip */
LDREG EXCDATA_IP(\t1), \t1
.endm
#else
.macro get_fault_ip t1 t2
- /* t1 = &__get_cpu_var(exception_data) */
+ /* t1 = this_cpu_ptr(&exception_data) */
addil LT%exception_data,%r27
LDREG RT%exception_data(%r1),\t2
/* t1 = t2->fault_ip */
prev parent reply other threads:[~2014-12-02 21:24 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 ` [PATCH 3/4] ia64: Update comment that references __get_cpu_var Christoph Lameter
2014-12-02 21:24 ` Christoph Lameter [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=20141202212440.031271472@linux.com \
--to=cl@linux.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linuxfoundation.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 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.