From: Alejandro Colomar <alx@kernel.org>
To: bugzilla-daemon@kernel.org
Cc: linux-man@vger.kernel.org
Subject: Re: [Bug 218018] dl_iterate_phdr should mention Elf64_Phdr (in addition to Elf32_Phdr).
Date: Mon, 1 Jan 2024 12:53:03 +0100 [thread overview]
Message-ID: <ZZKnn2Iyn2pWpbxy@debian> (raw)
In-Reply-To: <bug-218018-11311-B8AwJ7hI24@https.bugzilla.kernel.org/>
On Wed, Dec 27, 2023 at 04:47:48PM +0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=218018
>
> --- Comment #2 from Paul Pluzhnikov (ppluzhnikov@google.com) ---
> (In reply to Rajesh from comment #1)
>
> > Do you think the following would be helpful.
>
> Sure.
>
> > Replacing "These program headers are structures of the following form:" with
> > the following
> >
> > The ELF program header is described by the type Elf32_Phdr or Elf64_Phdr
> > depending on the architecture. Following is an example of 32 bit
> > architecture. Refer to elf (man elf) for more information on 64 bit
> > architecture.
>
> I suggest deleting the last 4 words, i.e.
>
> Refer to elf (man elf) for more information.
>
> since "man elf" describes both Elf{32,64}_Phdr in a bit more detail.
I suggest creating link pages Elf32_Phdr(3type) and Elf64_Phdr(3type)
both of which link to elf(5).
>
> --
> You may reply to this email to add a comment.
>
> You are receiving this mail because:
> You are watching the assignee of the bug.
--
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.
next prev parent reply other threads:[~2024-01-01 11:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 21:56 [Bug 218018] New: dl_iterate_phdr should mention Elf64_Phdr (in addition to Elf32_Phdr) bugzilla-daemon
2023-12-27 16:41 ` [Bug 218018] " bugzilla-daemon
2023-12-27 16:47 ` bugzilla-daemon
2024-01-01 11:53 ` Alejandro Colomar [this message]
2023-12-28 16:01 ` bugzilla-daemon
2024-01-01 11:53 ` bugzilla-daemon
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=ZZKnn2Iyn2pWpbxy@debian \
--to=alx@kernel.org \
--cc=bugzilla-daemon@kernel.org \
--cc=linux-man@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