From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: masahiroy@kernel.org, Mikhail.Petrov@mir.dev,
unixbhaskar@gmail.com, dbrazdil@google.com, maz@kernel.org,
linux-kernel@vger.kernel.org
Cc: rdunlap@infradead.org
Subject: [PATCH] scripts: Mere typo fixes in the file kallsyms.c
Date: Mon, 15 Mar 2021 04:02:00 +0530 [thread overview]
Message-ID: <20210314223200.218402-1-unixbhaskar@gmail.com> (raw)
Ordinary spelling fixes.
Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
---
scripts/kallsyms.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/kallsyms.c b/scripts/kallsyms.c
index 7ecd2ccba531..4d44aba8c212 100644
--- a/scripts/kallsyms.c
+++ b/scripts/kallsyms.c
@@ -12,7 +12,7 @@
* map char code 0xF7 to represent "write_" and then in every symbol where
* "write_" appears it can be replaced by 0xF7, saving 5 bytes.
* The used codes themselves are also placed in the table so that the
- * decompresion can work without "special cases".
+ * decompression can work without "special cases".
* Applied to kernel symbols, this usually produces a compression ratio
* of about 50%.
*
@@ -337,7 +337,7 @@ static void output_label(const char *label)
printf("%s:\n", label);
}
-/* Provide proper symbols relocatability by their '_text' relativeness. */
+/* Provide proper symbols relocate ability by their '_text' relativeness. */
static void output_address(unsigned long long addr)
{
if (_text <= addr)
--
2.30.2
next reply other threads:[~2021-03-14 22:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 22:32 Bhaskar Chowdhury [this message]
2021-03-14 23:59 ` [PATCH] scripts: Mere typo fixes in the file kallsyms.c 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=20210314223200.218402-1-unixbhaskar@gmail.com \
--to=unixbhaskar@gmail.com \
--cc=Mikhail.Petrov@mir.dev \
--cc=dbrazdil@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=maz@kernel.org \
--cc=rdunlap@infradead.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