From: "Gustavo A. R. Silva" <gustavoars@kernel.org>
To: Kees Cook <kees@kernel.org>
Cc: linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
"Gustavo A. R. Silva" <gustavoars@kernel.org>
Subject: [PATCH 0/2][next] Expand TRAILING_OVERLAP() capabilities
Date: Wed, 17 Sep 2025 15:25:44 +0200 [thread overview]
Message-ID: <cover.1758115257.git.gustavoars@kernel.org> (raw)
Small series aimed at expanding TRAILING_OVERLAP() capabilities.
Gustavo A. R. Silva (2):
stddef: Remove token-pasting in TRAILING_OVERLAP()
stddef: Introduce __TRAILING_OVERLAP()
include/linux/stddef.h | 24 ++++++++++++++++++++----
1 file changed, 20 insertions(+), 4 deletions(-)
--
2.43.0
next reply other threads:[~2025-09-17 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 13:25 Gustavo A. R. Silva [this message]
2025-09-17 13:26 ` [PATCH 1/2][next] stddef: Remove token-pasting in TRAILING_OVERLAP() Gustavo A. R. Silva
2025-09-17 13:28 ` [PATCH 2/2][next] stddef: Introduce __TRAILING_OVERLAP() Gustavo A. R. Silva
2025-09-17 16:30 ` [PATCH 0/2][next] Expand TRAILING_OVERLAP() capabilities Kees Cook
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=cover.1758115257.git.gustavoars@kernel.org \
--to=gustavoars@kernel.org \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).