From: Randy Dunlap <rdunlap@infradead.org>
To: LKML <linux-kernel@vger.kernel.org>,
Vineet Gupta <vgupta@synopsys.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>
Subject: [PATCH] arc: include/asm: fix typos of "themselves"
Date: Mon, 5 Oct 2020 20:30:00 -0700 [thread overview]
Message-ID: <610cc0df-deac-e2f6-e9ce-b19b3cba9501@infradead.org> (raw)
From: Randy Dunlap <rdunlap@infradead.org>
Fix copy/paste spello of "themselves" in 3 places.
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Vineet Gupta <vgupta@synopsys.com>
Cc: linux-snps-arc@lists.infradead.org
---
arch/arc/include/asm/atomic.h | 4 ++--
arch/arc/include/asm/cmpxchg.h | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
--- lnx-59-rc7.orig/arch/arc/include/asm/atomic.h
+++ lnx-59-rc7/arch/arc/include/asm/atomic.h
@@ -45,7 +45,7 @@ static inline int atomic_##op##_return(i
\
/* \
* Explicit full memory barrier needed before/after as \
- * LLOCK/SCOND thmeselves don't provide any such semantics \
+ * LLOCK/SCOND themselves don't provide any such semantics \
*/ \
smp_mb(); \
\
@@ -71,7 +71,7 @@ static inline int atomic_fetch_##op(int
\
/* \
* Explicit full memory barrier needed before/after as \
- * LLOCK/SCOND thmeselves don't provide any such semantics \
+ * LLOCK/SCOND themselves don't provide any such semantics \
*/ \
smp_mb(); \
\
--- lnx-59-rc7.orig/arch/arc/include/asm/cmpxchg.h
+++ lnx-59-rc7/arch/arc/include/asm/cmpxchg.h
@@ -20,7 +20,7 @@ __cmpxchg(volatile void *ptr, unsigned l
/*
* Explicit full memory barrier needed before/after as
- * LLOCK/SCOND thmeselves don't provide any such semantics
+ * LLOCK/SCOND themselves don't provide any such semantics
*/
smp_mb();
next reply other threads:[~2020-10-06 3:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 3:30 Randy Dunlap [this message]
2020-10-06 4:07 ` Vineet Gupta
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=610cc0df-deac-e2f6-e9ce-b19b3cba9501@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=vgupta@synopsys.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
all inboxes | Powered by JetHome®