linux-kernel - [tip: core/rcu] tools/nolibc: Fix a spelling error in a comment

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>] [day] [month] [year] [list]

Message-ID: <160788606676.3364.14206290151138290950.tip-bot2@tip-bot2>
Date:   Sun, 13 Dec 2020 19:01:06 -0000
From:   "tip-bot2 for Bhaskar Chowdhury" <tip-bot2@...utronix.de>
To:     linux-tip-commits@...r.kernel.org
Cc:     Bhaskar Chowdhury <unixbhaskar@...il.com>,
        Willy Tarreau <w@....eu>,
        "Paul E. McKenney" <paulmck@...nel.org>, x86@...nel.org,
        linux-kernel@...r.kernel.org
Subject: [tip: core/rcu] tools/nolibc: Fix a spelling error in a comment

The following commit has been merged into the core/rcu branch of tip:

Commit-ID:     06dc8d4591b8d8ce0ece94474718b53f0a5c5de3
Gitweb:        https://git.kernel.org/tip/06dc8d4591b8d8ce0ece94474718b53f0a5c5de3
Author:        Bhaskar Chowdhury <unixbhaskar@...il.com>
AuthorDate:    Tue, 20 Oct 2020 21:22:56 +02:00
Committer:     Paul E. McKenney <paulmck@...nel.org>
CommitterDate: Fri, 06 Nov 2020 17:13:58 -08:00

tools/nolibc:  Fix a spelling error in a comment

Fix a spelling in the comment line.

s/memry/memory/p

This is on linux-next.

Signed-off-by: Bhaskar Chowdhury <unixbhaskar@...il.com>
Signed-off-by: Willy Tarreau <w@....eu>
Signed-off-by: Paul E. McKenney <paulmck@...nel.org>
---
 tools/include/nolibc/nolibc.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/include/nolibc/nolibc.h b/tools/include/nolibc/nolibc.h
index d6d2623..e61d36c 100644
--- a/tools/include/nolibc/nolibc.h
+++ b/tools/include/nolibc/nolibc.h
@@ -107,7 +107,7 @@ static int errno;
 #endif
 
 /* errno codes all ensure that they will not conflict with a valid pointer
- * because they all correspond to the highest addressable memry page.
+ * because they all correspond to the highest addressable memory page.
  */
 #define MAX_ERRNO 4095