From: Andrew Kreimer <algonell@gmail.com>
To: smatch@vger.kernel.org
Cc: Andrew Kreimer <algonell@gmail.com>
Subject: [PATCH 1/2] doc: fix typos
Date: Wed, 16 Oct 2024 18:49:18 +0300 [thread overview]
Message-ID: <20241016154919.3323-1-algonell@gmail.com> (raw)
Fix typos via codespell.
Signed-off-by: Andrew Kreimer <algonell@gmail.com>
---
Documentation/arm64-detecting-tagged-addresses.txt | 2 +-
Documentation/sparse-README.txt | 2 +-
Documentation/sphinx/ir.py | 2 +-
Documentation/types.rst | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/arm64-detecting-tagged-addresses.txt b/Documentation/arm64-detecting-tagged-addresses.txt
index 0f421c82..f9541b82 100644
--- a/Documentation/arm64-detecting-tagged-addresses.txt
+++ b/Documentation/arm64-detecting-tagged-addresses.txt
@@ -179,7 +179,7 @@ annotation - therefore it is not necessary to use the annotation in every
function that do_mmap calls. When using this annotation smdb.py will filter
out functions that carry a value which has been annotated as untagged. Please
note that due to limitations in parameter tracking some annotations will be
-ignored and not propogated all the way down the call tree.
+ignored and not propagated all the way down the call tree.
Finally, the following patch is required to add annotations to the Linux
kernel:
diff --git a/Documentation/sparse-README.txt b/Documentation/sparse-README.txt
index 033ae15d..63f752b5 100644
--- a/Documentation/sparse-README.txt
+++ b/Documentation/sparse-README.txt
@@ -62,7 +62,7 @@ more requirements. The user is free to do whatever he wants with the
parse tree that got built up, and needs not worry about the library ever
again. There is no extra state, there are no parser callbacks, there is
only the parse tree that is described by the header files. The action
-funtion takes a pointer to a symbol_list and does whatever it likes with it.
+function takes a pointer to a symbol_list and does whatever it likes with it.
The library also contains (as an example user) a few clients that do the
preprocessing, parsing and type evaluation and just print out the
diff --git a/Documentation/sphinx/ir.py b/Documentation/sphinx/ir.py
index 3028200a..c26b3716 100755
--- a/Documentation/sphinx/ir.py
+++ b/Documentation/sphinx/ir.py
@@ -24,7 +24,7 @@ import sphinx
class IROpDirective(docutils.parsers.rst.Directive):
# use the first line of content as the argument, this allow
- # to not have to write a blanck line after the directive
+ # to not have to write a blank line after the directive
final_argument_whitespace = True
required_argument = 0
#optional_arguments = 0
diff --git a/Documentation/types.rst b/Documentation/types.rst
index 974f9861..b7c97870 100644
--- a/Documentation/types.rst
+++ b/Documentation/types.rst
@@ -37,7 +37,7 @@ Some bits, also related to the type, are in struct symbol itself:
attributes. It's also used internally to keep track of some states
(MOD_ACCESS or MOD_ADDRESSABLE).
* ``alignment`` is used for the alignment, in bytes.
-* ``contexts`` is used to store the informations associated with the
+* ``contexts`` is used to store the information associated with the
attribute ``context()``.
* ``as`` is used to hold the identifier of the attribute ``address_space()``.
--
2.39.5
next reply other threads:[~2024-10-16 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 15:49 Andrew Kreimer [this message]
2024-10-16 15:49 ` [PATCH 2/2] scripts: fix typos Andrew Kreimer
2024-10-16 16:26 ` [PATCH 1/2] doc: " Dan Carpenter
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=20241016154919.3323-1-algonell@gmail.com \
--to=algonell@gmail.com \
--cc=smatch@vger.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