linux-kernel - [tip: x86/cleanups] x86/mm: Remove repeated word in comments

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <168613512909.404.6478565511895362622.tip-bot2@tip-bot2>
Date:   Wed, 07 Jun 2023 10:52:09 -0000
From:   "tip-bot2 for Bo Liu" <tip-bot2@...utronix.de>
To:     linux-tip-commits@...r.kernel.org
Cc:     Bo Liu <liubo03@...pur.com>,
        "Borislav Petkov (AMD)" <bp@...en8.de>, x86@...nel.org,
        linux-kernel@...r.kernel.org
Subject: [tip: x86/cleanups] x86/mm: Remove repeated word in comments

The following commit has been merged into the x86/cleanups branch of tip:

Commit-ID:     7e980867ced0037a65f588971b89769857b77aab
Gitweb:        https://git.kernel.org/tip/7e980867ced0037a65f588971b89769857b77aab
Author:        Bo Liu <liubo03@...pur.com>
AuthorDate:    Thu, 04 May 2023 04:54:46 -04:00
Committer:     Borislav Petkov (AMD) <bp@...en8.de>
CommitterDate: Wed, 07 Jun 2023 12:47:34 +02:00

x86/mm: Remove repeated word in comments

Remove the repeated word "the" in comments.

Signed-off-by: Bo Liu <liubo03@...pur.com>
Signed-off-by: Borislav Petkov (AMD) <bp@...en8.de>
Link: https://lore.kernel.org/r/20230504085446.2574-1-liubo03@inspur.com
---
 arch/x86/mm/pat/set_memory.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/x86/mm/pat/set_memory.c b/arch/x86/mm/pat/set_memory.c
index 7159cf7..b18fe0d 100644
--- a/arch/x86/mm/pat/set_memory.c
+++ b/arch/x86/mm/pat/set_memory.c
@@ -231,7 +231,7 @@ within_inclusive(unsigned long addr, unsigned long start, unsigned long end)
  * points to #2, but almost all physical-to-virtual translations point to #1.
  *
  * This is so that we can have both a directmap of all physical memory *and*
- * take full advantage of the the limited (s32) immediate addressing range (2G)
+ * take full advantage of the limited (s32) immediate addressing range (2G)
  * of x86_64.
  *
  * See Documentation/arch/x86/x86_64/mm.rst for more detail.