From: "Dmitry V. Levin" <ldv@altlinux.org>
To: elfutils-devel@sourceware.org
Subject: [PATCH 05/12] libcpu: fix spelling typos in comments
Date: Sat, 12 Dec 2020 19:50:57 +0300 [thread overview]
Message-ID: <20201212165057.GE503@altlinux.org> (raw)
In-Reply-To: <20201212164901.GA474@altlinux.org>
layed -> laid
adressing -> addressing
Signed-off-by: Dmitry V. Levin <ldv@altlinux.org>
---
libcpu/ChangeLog | 5 +++++
libcpu/bpf_disasm.c | 2 +-
libcpu/i386_disasm.c | 2 +-
3 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/libcpu/ChangeLog b/libcpu/ChangeLog
index a342b7f6..000105bf 100644
--- a/libcpu/ChangeLog
+++ b/libcpu/ChangeLog
@@ -1,3 +1,8 @@
+2020-12-12 Dmitry V. Levin <ldv@altlinux.org>
+
+ * bpf_disasm.c (bswap_bpf_insn): Fix spelling typo in comment.
+ * i386_disasm.c (i386_disasm): Likewise.
+
2020-05-09 Mark Wielaard <mark@klomp.org>
* i386_parse.y (new_bitfield): Call free newp on error.
diff --git a/libcpu/bpf_disasm.c b/libcpu/bpf_disasm.c
index 3d92d014..62643c81 100644
--- a/libcpu/bpf_disasm.c
+++ b/libcpu/bpf_disasm.c
@@ -74,7 +74,7 @@ static void
bswap_bpf_insn (struct bpf_insn *p)
{
/* Note that the dst_reg and src_reg fields are 4-bit bitfields.
- That means these two nibbles are (typically) layed out in the
+ That means these two nibbles are (typically) laid out in the
opposite order between big- and little-endian hosts. This is
not required by any standard, but does happen to be true for
at least ppc, s390, arm and mips as big-endian hosts. */
diff --git a/libcpu/i386_disasm.c b/libcpu/i386_disasm.c
index 32df8cd0..fd7340cc 100644
--- a/libcpu/i386_disasm.c
+++ b/libcpu/i386_disasm.c
@@ -588,7 +588,7 @@ i386_disasm (Ebl *ebl __attribute__((unused)),
}
/* We have a match. First determine how many bytes are
- needed for the adressing mode. */
+ needed for the addressing mode. */
param_start = codep;
if (instrtab[cnt].modrm)
{
--
ldv
next prev parent reply other threads:[~2020-12-12 16:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 16:49 [PATCH 00/12] Fix spelling typos in comments, tests, and text files Dmitry V. Levin
2020-12-12 16:50 ` [PATCH 01/12] debuginfod: fix spelling typos in error diagnostics and comments Dmitry V. Levin
2020-12-12 16:50 ` [PATCH 02/12] backends: fix spelling typos in comments Dmitry V. Levin
2020-12-12 16:50 ` [PATCH 03/12] config: fix spelling typos in comments and %changelog Dmitry V. Levin
2020-12-12 16:50 ` [PATCH 04/12] libasm: fix spelling typos in comments Dmitry V. Levin
2020-12-12 16:50 ` Dmitry V. Levin [this message]
2020-12-12 16:51 ` [PATCH 06/12] libdw: fix spelling typos in comments and ChangeLog Dmitry V. Levin
2020-12-12 16:51 ` [PATCH 07/12] libdwelf: fix spelling typos in comments Dmitry V. Levin
2020-12-12 16:51 ` [PATCH 08/12] libdwfl: fix spelling typos in comments and ChangeLog Dmitry V. Levin
2020-12-12 16:52 ` [PATCH 09/12] libelf: fix spelling typos in comments Dmitry V. Levin
2020-12-12 16:52 ` [PATCH 10/12] src: fix spelling typos in comments and ChangeLog Dmitry V. Levin
2020-12-12 16:52 ` [PATCH 11/12] tests: fix spelling typos in error diagnostics and comments Dmitry V. Levin
2020-12-12 16:52 ` [PATCH 12/12] Fix spelling typos in NEWS, NOTES, TODO, and in comments of configure.ac Dmitry V. Levin
2020-12-12 17:17 ` [PATCH 00/12] Fix spelling typos in comments, tests, and text files Mark Wielaard
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=20201212165057.GE503@altlinux.org \
--to=ldv@altlinux.org \
--cc=elfutils-devel@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).