From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Will Deacon <will.deacon@arm.com>
Cc: linux-arch@vger.kernel.org
Subject: Re: [RFC PATCH 02/16] arc: locks: remove unused arch_*_relax operations
Date: Mon, 24 Jun 2013 09:42:25 +0530 [thread overview]
Message-ID: <51C7C729.2080601@synopsys.com> (raw)
In-Reply-To: <1371835057-19335-3-git-send-email-will.deacon@arm.com>
Hi Will,
On 06/21/2013 10:47 PM, Will Deacon wrote:
> The arch_{spin,read,write}_relax macros are not used anywhere in the
> kernel and are typically just aliases for cpu_relax().
>
> This patch removes the unused definitions for Arc.
For consistency sake, can you please uppercase to ARC in changelog above. Same
goes for arc prefix in patch subject.
>
> Cc: Vineet Gupta <vgupta@synopsys.com>
> Signed-off-by: Will Deacon <will.deacon@arm.com>
Acked-by: Vineet Gupta <vgupta@synopsys.com>
Thx,
-Vineet
> ---
> arch/arc/include/asm/spinlock.h | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/arch/arc/include/asm/spinlock.h b/arch/arc/include/asm/spinlock.h
> index f158197..fddced5 100644
> --- a/arch/arc/include/asm/spinlock.h
> +++ b/arch/arc/include/asm/spinlock.h
> @@ -137,8 +137,4 @@ static inline void arch_write_unlock(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()
> -
> #endif /* __ASM_SPINLOCK_H */
next prev parent reply other threads:[~2013-06-24 4:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 17:17 [RFC PATCH 00/16] Remove unused arch_*_relax operations from spinlocks Will Deacon
2013-06-21 17:17 ` [RFC PATCH 01/16] alpha: locks: remove unused arch_*_relax operations Will Deacon
2013-06-21 17:17 ` [RFC PATCH 02/16] arc: " Will Deacon
2013-06-24 4:12 ` Vineet Gupta [this message]
2013-06-24 8:58 ` Will Deacon
2013-06-21 17:17 ` [RFC PATCH 03/16] ARM: " Will Deacon
2013-06-21 17:17 ` [RFC PATCH 04/16] arm64: " Will Deacon
2013-06-21 17:17 ` [RFC PATCH 05/16] blackfin: " Will Deacon
2013-06-21 17:17 ` [RFC PATCH 06/16] cris: " Will Deacon
2013-06-24 6:41 ` Jesper Nilsson
2013-06-21 17:17 ` [RFC PATCH 07/16] ia64: " Will Deacon
2013-06-21 17:17 ` [RFC PATCH 08/16] m32r: " Will Deacon
2013-06-21 17:17 ` [RFC PATCH 09/16] metag: " Will Deacon
2013-06-24 9:07 ` James Hogan
2013-06-21 17:17 ` [RFC PATCH 10/16] mips: " Will Deacon
2013-06-21 17:48 ` David Daney
2013-06-21 17:17 ` [RFC PATCH 11/16] hppa: " Will Deacon
2013-06-21 17:17 ` [RFC PATCH 12/16] powerpc: " Will Deacon
2013-06-21 22:16 ` Benjamin Herrenschmidt
2013-06-21 17:17 ` [RFC PATCH 13/16] s390: " Will Deacon
2013-06-21 17:17 ` [RFC PATCH 14/16] sh: " Will Deacon
2013-06-21 17:17 ` [RFC PATCH 15/16] sparc: " Will Deacon
2013-06-21 19:18 ` David Miller
2013-06-21 17:17 ` [RFC PATCH 16/16] x86: " Will Deacon
2013-06-21 20:48 ` Thomas Gleixner
2013-06-24 11:58 ` [RFC PATCH 00/16] Remove unused arch_*_relax operations from spinlocks Will Deacon
2013-06-28 7:31 ` Martin Schwidefsky
2013-07-01 8:53 ` Will Deacon
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=51C7C729.2080601@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=linux-arch@vger.kernel.org \
--cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).