From: Helge Deller <deller@gmx.de>
To: Parisc List <linux-parisc@vger.kernel.org>
Subject: Fwd: [PATCH RESEND 10/14] hppa: locks: remove redundant arch_*_relax operations
Date: Wed, 05 Mar 2014 21:38:14 +0100 [thread overview]
Message-ID: <53178B36.2070307@gmx.de> (raw)
In-Reply-To: <1393004101-25382-11-git-send-email-will.deacon@arm.com>
Forwarding to parisc patchwork...
-------- Original Message --------
Subject: [PATCH RESEND 10/14] hppa: locks: remove redundant
arch_*_relax operations
Date: Fri, 21 Feb 2014 17:34:57 +0000
From: Will Deacon <will.deacon@arm.com>
To: akpm@linux-foundation.org
CC: linux-arch@vger.kernel.org, Will Deacon <will.deacon@arm.com>,
Helge Deller <deller@gmx.de>
Now that the arch_{spin,read,write}_relax macros default to cpu_relax(),
remove the redundant definitions for parisc.
Cc: Helge Deller <deller@gmx.de>
Signed-off-by: Will Deacon <will.deacon@arm.com>
---
arch/parisc/include/asm/spinlock.h | 4 ----
1 file changed, 4 deletions(-)
diff --git a/arch/parisc/include/asm/spinlock.h b/arch/parisc/include/asm/spinlock.h
index 3516e0b27044..64f2992e439f 100644
--- a/arch/parisc/include/asm/spinlock.h
+++ b/arch/parisc/include/asm/spinlock.h
@@ -191,8 +191,4 @@ static __inline__ int arch_write_can_lock(arch_rwlock_t *rw)
#define arch_read_lock_flags(lock, flags) arch_read_lock(lock)
#define arch_write_lock_flags(lock, flags) arch_write_lock(lock)
-#define arch_spin_relax(lock) cpu_relax()
-#define arch_read_relax(lock) cpu_relax()
-#define arch_write_relax(lock) cpu_relax()
parent reply other threads:[~2014-03-05 20:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1393004101-25382-11-git-send-email-will.deacon@arm.com>]
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=53178B36.2070307@gmx.de \
--to=deller@gmx.de \
--cc=linux-parisc@vger.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