* [PATCH] arc: include/asm: Couple of spelling fixes
@ 2021-03-22 12:32 Bhaskar Chowdhury
2021-03-22 18:43 ` Randy Dunlap
0 siblings, 1 reply; 2+ messages in thread
From: Bhaskar Chowdhury @ 2021-03-22 12:32 UTC (permalink / raw
To: vgupta, rdunlap, unixbhaskar, linux-snps-arc, linux-kernel
s/interrpted/interrupted/
s/defintion/definition/
Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
---
arch/arc/include/asm/cmpxchg.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arc/include/asm/cmpxchg.h b/arch/arc/include/asm/cmpxchg.h
index 9b87e162e539..dfeffa25499b 100644
--- a/arch/arc/include/asm/cmpxchg.h
+++ b/arch/arc/include/asm/cmpxchg.h
@@ -116,7 +116,7 @@ static inline unsigned long __xchg(unsigned long val, volatile void *ptr,
*
* Technically the lock is also needed for UP (boils down to irq save/restore)
* but we can cheat a bit since cmpxchg() atomic_ops_lock() would cause irqs to
- * be disabled thus can't possibly be interrpted/preempted/clobbered by xchg()
+ * be disabled thus can't possibly be interrupted/preempted/clobbered by xchg()
* Other way around, xchg is one instruction anyways, so can't be interrupted
* as such
*/
@@ -143,7 +143,7 @@ static inline unsigned long __xchg(unsigned long val, volatile void *ptr,
/*
* "atomic" variant of xchg()
* REQ: It needs to follow the same serialization rules as other atomic_xxx()
- * Since xchg() doesn't always do that, it would seem that following defintion
+ * Since xchg() doesn't always do that, it would seem that following definition
* is incorrect. But here's the rationale:
* SMP : Even xchg() takes the atomic_ops_lock, so OK.
* LLSC: atomic_ops_lock are not relevant at all (even if SMP, since LLSC
--
2.31.0
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] arc: include/asm: Couple of spelling fixes
2021-03-22 12:32 [PATCH] arc: include/asm: Couple of spelling fixes Bhaskar Chowdhury
@ 2021-03-22 18:43 ` Randy Dunlap
0 siblings, 0 replies; 2+ messages in thread
From: Randy Dunlap @ 2021-03-22 18:43 UTC (permalink / raw
To: Bhaskar Chowdhury, vgupta, linux-snps-arc, linux-kernel
On 3/22/21 5:32 AM, Bhaskar Chowdhury wrote:
>
> s/interrpted/interrupted/
> s/defintion/definition/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> arch/arc/include/asm/cmpxchg.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arc/include/asm/cmpxchg.h b/arch/arc/include/asm/cmpxchg.h
> index 9b87e162e539..dfeffa25499b 100644
> --- a/arch/arc/include/asm/cmpxchg.h
> +++ b/arch/arc/include/asm/cmpxchg.h
> @@ -116,7 +116,7 @@ static inline unsigned long __xchg(unsigned long val, volatile void *ptr,
> *
> * Technically the lock is also needed for UP (boils down to irq save/restore)
> * but we can cheat a bit since cmpxchg() atomic_ops_lock() would cause irqs to
> - * be disabled thus can't possibly be interrpted/preempted/clobbered by xchg()
> + * be disabled thus can't possibly be interrupted/preempted/clobbered by xchg()
> * Other way around, xchg is one instruction anyways, so can't be interrupted
> * as such
> */
> @@ -143,7 +143,7 @@ static inline unsigned long __xchg(unsigned long val, volatile void *ptr,
> /*
> * "atomic" variant of xchg()
> * REQ: It needs to follow the same serialization rules as other atomic_xxx()
> - * Since xchg() doesn't always do that, it would seem that following defintion
> + * Since xchg() doesn't always do that, it would seem that following definition
> * is incorrect. But here's the rationale:
> * SMP : Even xchg() takes the atomic_ops_lock, so OK.
> * LLSC: atomic_ops_lock are not relevant at all (even if SMP, since LLSC
> --
--
~Randy
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-03-22 18:44 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-03-22 12:32 [PATCH] arc: include/asm: Couple of spelling fixes Bhaskar Chowdhury
2021-03-22 18:43 ` Randy Dunlap
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 read-only IMAP folder(s) and NNTP newsgroup(s).