From: Charlie Jenkins <thecharlesjenkins@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Kees Cook <kees@kernel.org>
Cc: linux-doc@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Charlie Jenkins <thecharlesjenkins@gmail.com>
Subject: [PATCH 0/2] Documentation/binfmt-misc.rst: Clarify "P" flag
Date: Sun, 19 Apr 2026 00:11:01 -0400 [thread overview]
Message-ID: <20260419-binfmt_misc_doc_update_p-v1-0-757c12f33cc2@gmail.com> (raw)
Improve the wording of the description of the "P" flag to explain that
the interpreter gets the path to the file provided by execve and not the
full path as well as documenting that AT_FLAGS can be read to see if the
"P" flag is set.
Signed-off-by: Charlie Jenkins <thecharlesjenkins@gmail.com>
---
Charlie Jenkins (2):
Documentation/binfmt-misc.rst: Include AT_FLAGS info in "P" flag description
Documenation/binfmt-misc.rst: Make "P" flag path desc more precise
Documentation/admin-guide/binfmt-misc.rst | 18 ++++++++++--------
1 file changed, 10 insertions(+), 8 deletions(-)
---
base-commit: 028ef9c96e96197026887c0f092424679298aae8
change-id: ${change-id}
- Charlie
next reply other threads:[~2026-04-19 4:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-19 4:11 Charlie Jenkins [this message]
2026-04-19 4:11 ` [PATCH 1/2] Documentation/binfmt-misc.rst: Include AT_FLAGS info in "P" flag description Charlie Jenkins
2026-04-19 4:11 ` [PATCH 2/2] Documenation/binfmt-misc.rst: Make "P" flag path desc more precise Charlie Jenkins
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=20260419-binfmt_misc_doc_update_p-v1-0-757c12f33cc2@gmail.com \
--to=thecharlesjenkins@gmail.com \
--cc=corbet@lwn.net \
--cc=kees@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=skhan@linuxfoundation.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