From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org
Subject: [PATCH 2/3] x86: cmpxchg_32.h: delete duplicated word
Date: Sat, 25 Jul 2020 17:41:23 -0700 [thread overview]
Message-ID: <20200726004124.20618-3-rdunlap@infradead.org> (raw)
In-Reply-To: <20200726004124.20618-1-rdunlap@infradead.org>
Delete the repeated word "you".
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Borislav Petkov <bp@alien8.de>
Cc: x86@kernel.org
---
arch/x86/include/asm/cmpxchg_32.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next-20200720.orig/arch/x86/include/asm/cmpxchg_32.h
+++ linux-next-20200720/arch/x86/include/asm/cmpxchg_32.h
@@ -3,7 +3,7 @@
#define _ASM_X86_CMPXCHG_32_H
/*
- * Note: if you use set64_bit(), __cmpxchg64(), or their variants, you
+ * Note: if you use set64_bit(), __cmpxchg64(), or their variants,
* you need to test for the feature in boot_cpu_data.
*/
next prev parent reply other threads:[~2020-07-26 0:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-26 0:41 [PATCH 0/3] x86: delete duplicated words Randy Dunlap
2020-07-26 0:41 ` [PATCH 1/3] x86: bootparam.h: delete duplicated word Randy Dunlap
2020-07-26 10:50 ` [tip: x86/cleanups] x86: bootparam.h: Delete " tip-bot2 for Randy Dunlap
2020-07-26 0:41 ` Randy Dunlap [this message]
2020-07-26 10:50 ` [tip: x86/cleanups] x86: cmpxchg_32.h: " tip-bot2 for Randy Dunlap
2020-07-26 0:41 ` [PATCH 3/3] x86: uv: uv_hub.h: delete " Randy Dunlap
2020-07-26 10:50 ` [tip: x86/cleanups] x86: uv: uv_hub.h: Delete " tip-bot2 for Randy Dunlap
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=20200726004124.20618-3-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®