From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] arm64: sigcontext.h: delete duplicated word
Date: Sat, 25 Jul 2020 17:32:07 -0700 [thread overview]
Message-ID: <20200726003207.20253-4-rdunlap@infradead.org> (raw)
In-Reply-To: <20200726003207.20253-1-rdunlap@infradead.org>
Drop the repeated word "the".
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org
---
arch/arm64/include/uapi/asm/sigcontext.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next-20200720.orig/arch/arm64/include/uapi/asm/sigcontext.h
+++ linux-next-20200720/arch/arm64/include/uapi/asm/sigcontext.h
@@ -179,7 +179,7 @@ struct sve_context {
* The same convention applies when returning from a signal: a caller
* will need to remove or resize the sve_context block if it wants to
* make the SVE registers live when they were previously non-live or
- * vice-versa. This may require the the caller to allocate fresh
+ * vice-versa. This may require the caller to allocate fresh
* memory and/or move other context blocks in the signal frame.
*
* Changing the vector length during signal return is not permitted:
next prev parent reply other threads:[~2020-07-26 0:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-26 0:32 [PATCH 0/3] arm64: delete duplicated words Randy Dunlap
2020-07-26 0:32 ` [PATCH 1/3] arm64: pgtable-hwdef.h: " Randy Dunlap
2020-07-26 0:32 ` [PATCH 2/3] arm64: ptrace.h: delete duplicated word Randy Dunlap
2020-07-26 0:32 ` Randy Dunlap [this message]
2020-07-30 12:23 ` [PATCH 0/3] arm64: delete duplicated words Catalin Marinas
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=20200726003207.20253-4-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will@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®