From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
akpm@linux-foundation.org
Cc: 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: Fri, 17 Mar 2023 15:22:28 +0700 [thread overview]
Message-ID: <ZBQjRLiXOwfmoIs+@debian.me> (raw)
In-Reply-To: <e262ea00-a027-9073-812e-7e034d75e718@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
On Tue, Mar 14, 2023 at 07:34:11PM -0700, Randy Dunlap wrote:
> Hi,
>
> [adding linux-doc for other interested parties]
Unfortunately akpm had already applied this doc as 60b38b7cbb295d ("ELF:
document some de-facto PT_* ABI quirks") while it being reviewed and
doesn't have any consensus yet.
> And could the document have a title, like:
>
> =========================
> ELF header usage in Linux
> =========================
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.
>
> (I just made that up. Feel free to change it. :)
>
> Also, the .rst file should be added to some chapter in the current
> documentation tree, such as under "Other documentation", so add this file name
> to Documentation/staging/index.rst. In fact this file could live in
> Documentation/staging instead of in Documentation/ELF/ (IMO of course).
If there are more ELF docs there then a separate directory may be
warranted.
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-03-17 8:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 17:02 [PATCH] ELF: document some de-facto PT_* ABI quirks Alexey Dobriyan
2023-03-15 2:34 ` Randy Dunlap
2023-03-17 8:22 ` Bagas Sanjaya [this message]
2023-03-17 16:53 ` Alexey Dobriyan
2023-03-19 12:52 ` Bagas Sanjaya
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=ZBQjRLiXOwfmoIs+@debian.me \
--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).