From: Nathan Chancellor <nathan@kernel.org>
To: Bill Wendling <morbo@google.com>
Cc: Kees Cook <kees@kernel.org>,
ardb@kernel.org, gustavoars@kernel.org, ndesaulniers@google.com,
justinstitt@google.com, broonie@kernel.org, elver@google.com,
alan.maguire@oracle.com, namjain@linux.microsoft.com,
peterz@infradead.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH v4] compiler_types: Allow opting out of __counted_by and __counted_by_ptr
Date: Wed, 7 Oct 2026 11:36:41 +0200 [thread overview]
Message-ID: <20261007093641.GA1527653@ax162> (raw)
In-Reply-To: <CAGG=3QXPAa-i4r3Vv6-q25A6EvsxGb5RDLn02z1=a5zo7W-7Vw@mail.gmail.com>
On Wed, Oct 07, 2026 at 02:32:45AM -0700, Bill Wendling wrote:
> Ard,
>
> What's the reason why x86 doesn't need the KBUILD_CFLAGS flags? Is
> there something that breaks things?
I think it is mostly historical. See Kees's series to address it:
https://lore.kernel.org/20261006204210.i.137-kees@kernel.org/
--
Cheers,
Nathan
next prev parent reply other threads:[~2026-10-07 9:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 10:25 [PATCH] " Bill Wendling
2026-10-05 10:44 ` Justin Stitt
2026-10-05 10:53 ` Ard Biesheuvel
2026-10-05 15:52 ` Bill Wendling
2026-10-05 19:19 ` Bill Wendling
2026-10-05 19:20 ` [PATCH v3] " Bill Wendling
2026-10-05 21:25 ` Ard Biesheuvel
2026-10-06 7:30 ` Justin Stitt
2026-10-06 8:07 ` Ard Biesheuvel
2026-10-06 9:23 ` Bill Wendling
2026-10-06 9:43 ` [PATCH v4] " Bill Wendling
2026-10-06 10:08 ` Ard Biesheuvel
2026-10-06 13:46 ` Bill Wendling
2026-10-06 14:12 ` Kees Cook
2026-10-07 9:09 ` Nathan Chancellor
2026-10-07 9:32 ` Bill Wendling
2026-10-07 9:36 ` Nathan Chancellor [this message]
2026-10-06 13:45 ` [PATCH v5] " Bill Wendling
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=20261007093641.GA1527653@ax162 \
--to=nathan@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=ardb@kernel.org \
--cc=broonie@kernel.org \
--cc=elver@google.com \
--cc=gustavoars@kernel.org \
--cc=justinstitt@google.com \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=namjain@linux.microsoft.com \
--cc=ndesaulniers@google.com \
--cc=peterz@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
all inboxes | Powered by JetHome®