From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] ELF: document some de-facto PT_* ABI quirks
Date: Sun, 19 Mar 2023 19:52:21 +0700 [thread overview]
Message-ID: <df9e53ac-be69-60a6-9782-73165873d28b@gmail.com> (raw)
In-Reply-To: <cc449f31-071c-48b8-a6a8-7b91f205c3c6@p183>
On 3/17/23 23:53, Alexey Dobriyan wrote:
>> The current doc path is Documentation/ELF/ELF.rst, which means that
>> readers expect to find general info about the executable format, not
>> some sort of trivia/niche like this.
>
> General info is in ELF spec. This document is intended to be Linux
> specific stuff you won't find anywhere but source.
>
> I'll write down overmapping rules as well.
In the same Documentation/ELF/ELF.rst?
And thus, the doc title should be "Linux-specific ELF notes", right?
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-03-19 12:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2acb586c-08a9-42d9-a41e-7986cc1383ea@p183>
2023-03-15 2:34 ` [PATCH] ELF: document some de-facto PT_* ABI quirks Randy Dunlap
2023-03-17 8:22 ` Bagas Sanjaya
2023-03-17 16:53 ` Alexey Dobriyan
2023-03-19 12:52 ` Bagas Sanjaya [this message]
2023-03-26 16:49 ` [PATCH v2] " Alexey Dobriyan
2023-03-26 19:51 ` Randy Dunlap
2023-03-29 16:40 ` Jonathan Corbet
2023-04-15 17:37 ` [PATCH v3] " Alexey Dobriyan
2023-04-20 16:07 ` Jonathan Corbet
2023-12-06 22:58 ` Kees Cook
2023-12-07 15:03 ` Eric W. Biederman
2023-12-10 11:45 ` Alexey Dobriyan
2023-12-10 22:58 ` Eric W. Biederman
2023-12-11 16:26 ` Alexey Dobriyan
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=df9e53ac-be69-60a6-9782-73165873d28b@gmail.com \
--to=bagasdotme@gmail.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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 NNTP newsgroup(s).