From: "Dmitry V. Levin" <ldv@altlinux.org>
To: elfutils-devel@sourceware.org
Subject: [PATCH 04/12] libasm: fix spelling typos in comments
Date: Sat, 12 Dec 2020 19:50:45 +0300 [thread overview]
Message-ID: <20201212165045.GD503@altlinux.org> (raw)
In-Reply-To: <20201212164901.GA474@altlinux.org>
endianess -> endianness
setion -> section
Signed-off-by: Dmitry V. Levin <ldv@altlinux.org>
---
libasm/ChangeLog | 5 +++++
libasm/asm_begin.c | 2 +-
libasm/asm_end.c | 2 +-
3 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/libasm/ChangeLog b/libasm/ChangeLog
index 6268b26c..78f1baa4 100644
--- a/libasm/ChangeLog
+++ b/libasm/ChangeLog
@@ -1,3 +1,8 @@
+2020-12-12 Dmitry V. Levin <ldv@altlinux.org>
+
+ * asm_begin.c (prepare_binary_output): Fix spelling typo in comment.
+ * asm_end.c (binary_end): Likewise.
+
2020-12-11 Dmitry V. Levin <ldv@altlinux.org>
* Makefile.am (GCC_INCLUDE): Remove.
diff --git a/libasm/asm_begin.c b/libasm/asm_begin.c
index 6248786c..1df2d4ea 100644
--- a/libasm/asm_begin.c
+++ b/libasm/asm_begin.c
@@ -98,7 +98,7 @@ prepare_binary_output (AsmCtx_t *result, Ebl *ebl)
/* Set the ELF version. */
ehdr->e_version = EV_CURRENT;
- /* Use the machine, class, and endianess values from the Ebl descriptor. */
+ /* Use the machine, class, and endianness values from the Ebl descriptor. */
ehdr->e_machine = ebl_get_elfmachine (ebl);
ehdr->e_ident[EI_CLASS] = class;
ehdr->e_ident[EI_DATA] = ebl_get_elfdata (ebl);
diff --git a/libasm/asm_end.c b/libasm/asm_end.c
index 3b8582fd..077d2aa5 100644
--- a/libasm/asm_end.c
+++ b/libasm/asm_end.c
@@ -257,7 +257,7 @@ binary_end (AsmCtx_t *ctx)
xndxdata->d_off = 0;
}
- /* Store the real section index in the extended setion
+ /* Store the real section index in the extended section
index table. */
assert ((size_t) ptr < ctx->nsymbol_tab + 1);
xshndx[ptr] = ndx;
--
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 ` Dmitry V. Levin [this message]
2020-12-12 16:50 ` [PATCH 05/12] libcpu: fix spelling typos in comments Dmitry V. Levin
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=20201212165045.GD503@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).