From: Kees Cook <kees@kernel.org>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: Kees Cook <kees@kernel.org>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v2][next] stddef: Document designated initializer semantics for __TRAILING_OVERLAP()
Date: Mon, 11 May 2026 12:18:54 -0700 [thread overview]
Message-ID: <177852713147.699524.16456484510741382829.b4-ty@kernel.org> (raw)
In-Reply-To: <agD0R-kNbg9YMOCT@kspp>
On Sun, 10 May 2026 15:10:31 -0600, Gustavo A. R. Silva wrote:
> Document the designated initializer behavior for overlapping storage
> between NAME and MEMBERS, and clarify the implications for static
> initialization to help avoid unintended overwrites.
>
>
Applied to for-next/hardening, thanks!
[1/1] stddef: Document designated initializer semantics for __TRAILING_OVERLAP()
https://git.kernel.org/kees/c/3c7495593752
Take care,
--
Kees Cook
prev parent reply other threads:[~2026-05-11 19:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-10 21:10 [PATCH v2][next] stddef: Document designated initializer semantics for __TRAILING_OVERLAP() Gustavo A. R. Silva
2026-05-11 19:18 ` Kees Cook [this message]
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=177852713147.699524.16456484510741382829.b4-ty@kernel.org \
--to=kees@kernel.org \
--cc=gustavoars@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