From: Alejandro Colomar <alx@kernel.org>
To: linux-api@vger.kernel.org
Cc: linux-man@vger.kernel.org, libc-alpha@sourceware.org,
Alejandro Colomar <alx@kernel.org>
Subject: [PATCH v1 0/2] uapi/linux/prctl: Use the L and UL integer suffixes for certain constants
Date: Tue, 28 May 2024 13:48:02 +0200 [thread overview]
Message-ID: <20240528114750.106187-1-alx@kernel.org> (raw)
In-Reply-To: <x6r3yc6l34g4k5g3tm6ywecdqux54xlpid7bp2fa7hvm43luc7@6fjgaxgm5uyj>
[-- Attachment #1: Type: text/plain, Size: 578 bytes --]
Alejandro Colomar (2):
uapi/linux/prctl: Use the L integer suffix for enumerations of width
long
uapi/linux/prctl: Use the UL integer suffix for bit fields of width
long
include/uapi/linux/prctl.h | 186 ++++++++++++++++++-------------------
1 file changed, 93 insertions(+), 93 deletions(-)
Range-diff against v0:
-: ------------ > 1: eb1cdf3e2f33 uapi/linux/prctl: Use the L integer suffix for enumerations of width long
-: ------------ > 2: 16f5bd565191 uapi/linux/prctl: Use the UL integer suffix for bit fields of width long
--
2.45.1
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-05-28 11:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-26 11:07 Sashimi of prctl(2) Alejandro Colomar
2024-05-26 11:27 ` Alejandro Colomar
2024-05-28 9:24 ` Correct way of calling prctl(2) (was: Sashimi of prctl(2)) Alejandro Colomar
2024-05-28 9:42 ` Alejandro Colomar
2024-05-28 11:48 ` Alejandro Colomar [this message]
2024-05-28 11:48 ` [PATCH v1 1/2] uapi/linux/prctl: Use the L integer suffix for enumerations of width long Alejandro Colomar
2024-05-28 11:48 ` [PATCH v1 2/2] uapi/linux/prctl: Use the UL integer suffix for bit fields " Alejandro Colomar
2024-06-12 12:02 ` [PATCH v1 0/2] uapi/linux/prctl: Use the L and UL integer suffixes for certain constants Alejandro Colomar
2024-05-28 15:20 ` Correct way of calling prctl(2) (was: Sashimi of prctl(2)) Xi Ruoyao
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=20240528114750.106187-1-alx@kernel.org \
--to=alx@kernel.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.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 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.