From: Alejandro Colomar <alx@kernel.org>
To: Ryota Saito <saito.ryota.23@shizuoka.ac.jp>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] man/man5/elf.5: Fix description of e_flags
Date: Fri, 7 Aug 2026 01:08:14 +0200 [thread overview]
Message-ID: <anUTx56mkeaPujq1@devuan> (raw)
In-Reply-To: <20260803130543.590173-1-saito.ryota.23@shizuoka.ac.jp>
[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]
Hi Ryota,
> Date: 2026-08-03 22:05:43+0900
> From: Ryota Saito <saito.ryota.23@shizuoka.ac.jp>
>
> Processor-specific e_flags are defined by the ABI supplements of many
> architectures (e.g., EF_RISCV_RVC, EF_ARM_EABI_VER5), and glibc's
> <elf.h> currently defines over 150 EF_* constants. Replace the
> incorrect statement with one that does not depend on the current set
> of defined flags.
>
> Signed-off-by: Ryota Saito <saito.ryota.23@shizuoka.ac.jp>
Thanks! I've applied the patch.
Have a lovely night!
Alex
> ---
> Range-diff:
> -: --------- > 1: 06a472163 man/man5/elf.5: Fix description of e_flags
>
> man/man5/elf.5 | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/man/man5/elf.5 b/man/man5/elf.5
> index 67544f4e6..ab5d2a21f 100644
> --- a/man/man5/elf.5
> +++ b/man/man5/elf.5
> @@ -509,7 +509,8 @@ file has no section header table, this member holds zero.
> .I e_flags
> This member holds processor-specific flags associated with the file.
> Flag names take the form EF_`machine_flag'.
> -Currently, no flags have been defined.
> +The defined flags and their meanings
> +depend on the target architecture and its ABI.
> .TP
> .I e_ehsize
> This member holds the ELF header's size in bytes.
> --
> 2.43.0
>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-08-06 23:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 13:05 [PATCH] man/man5/elf.5: Fix description of e_flags Ryota Saito
2026-08-06 23:08 ` Alejandro Colomar [this message]
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=anUTx56mkeaPujq1@devuan \
--to=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=saito.ryota.23@shizuoka.ac.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.