From: Martin Weiss <martin.githubacc@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Martin Weiss <Martin.weiss2410@gmail.com>,
Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nsc@kernel.org>,
Ihor Solodrai <ihor.solodrai@linux.dev>,
Alexei Starovoitov <ast@kernel.org>,
Ard Biesheuvel <ardb@kernel.org>,
Alexey Gladkov <legion@kernel.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kbuild@vger.kernel.org
Subject: [PATCH 1/4] scripts: fix spelling mistakes
Date: Mon, 29 Jun 2026 15:28:06 +0700 [thread overview]
Message-ID: <20260629082812.551273-1-Martin.weiss2410@gmail.com> (raw)
Signed-off-by: Martin Weiss <Martin.weiss2410@gmail.com>
---
scripts/config | 2 +-
scripts/link-vmlinux.sh | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/config b/scripts/config
index ea475c07de28..dfa78cfcba67 100755
--- a/scripts/config
+++ b/scripts/config
@@ -38,7 +38,7 @@ commands:
options:
--file config-file .config file to change (default .config)
- --keep-case|-k Keep next symbols' case (dont' upper-case it)
+ --keep-case|-k Keep next symbols' case (don't upper-case it)
$myname doesn't check the validity of the .config file. This is done at next
make time.
diff --git a/scripts/link-vmlinux.sh b/scripts/link-vmlinux.sh
index f99e196abeea..c8f27e4175f9 100755
--- a/scripts/link-vmlinux.sh
+++ b/scripts/link-vmlinux.sh
@@ -38,7 +38,7 @@ is_enabled() {
}
# Nice output in kbuild format
-# Will be supressed by "make -s"
+# Will be suppressed by "make -s"
info()
{
printf " %-7s %s\n" "${1}" "${2}"
--
2.54.0
next reply other threads:[~2026-06-29 8:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 8:28 Martin Weiss [this message]
2026-06-29 8:28 ` [PATCH 2/4] selftests: filesystems: fix spelling mistake in statmount test Martin Weiss
2026-06-29 8:28 ` [PATCH 3/4] selftests: powerpc: fix spelling mistake Martin Weiss
2026-06-29 8:28 ` [PATCH 4/4] tools/build: fix spelling mistake in documentation Martin Weiss
2026-06-30 2:03 ` [PATCH 1/4] scripts: fix spelling mistakes Nathan Chancellor
2026-07-08 4:23 ` Randy Dunlap
2026-07-17 12:55 ` Nicolas Schier
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=20260629082812.551273-1-Martin.weiss2410@gmail.com \
--to=martin.githubacc@gmail.com \
--cc=Martin.weiss2410@gmail.com \
--cc=ardb@kernel.org \
--cc=ast@kernel.org \
--cc=ihor.solodrai@linux.dev \
--cc=jpoimboe@kernel.org \
--cc=legion@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=rostedt@goodmis.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®