From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Eric Biggers <ebiggers@kernel.org>,
Ard Biesheuvel <ardb@kernel.org>,
Ard Biesheuvel <ardb+git@google.com>,
linux-crypto@vger.kernel.org, arnd@arndb.de,
Kees Cook <kees@kernel.org>
Subject: Re: [RFC PATCH] libcrypto/chachapoly: Use strict typing for fixed size array arguments
Date: Sat, 15 Nov 2025 18:39:26 +0100 [thread overview]
Message-ID: <aRi6zrH3sGyTZcmf@zx2c4.com> (raw)
In-Reply-To: <CAHk-=wj6J5L5Y+oHc-i9BrDONpSbtt=iEemcyUm3dYnZ3pXxxg@mail.gmail.com>
Hi Linus,
On Sat, Nov 15, 2025 at 09:11:31AM -0800, Linus Torvalds wrote:
> So *if* we end up using this syntax more widely, I suspect we'd want
> to have a macro that makes the semantics more obvious, even if it's
> something silly and trivial like
>
> #define min_array_size(n) static n
>
> just so that people who aren't familiar with that crazy syntax
> understand what it means.
Oh that's a good suggestion. I'll see if I can rig that up and send
something.
Jason
next prev parent reply other threads:[~2025-11-15 17:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 18:07 [RFC PATCH] libcrypto/chachapoly: Use strict typing for fixed size array arguments Ard Biesheuvel
2025-11-14 20:23 ` Jason A. Donenfeld
2025-11-14 20:33 ` Ard Biesheuvel
2025-11-15 2:14 ` Eric Biggers
2025-11-15 17:11 ` Linus Torvalds
2025-11-15 17:32 ` Linus Torvalds
2025-11-15 17:39 ` Jason A. Donenfeld [this message]
2025-12-02 1:12 ` Alejandro Colomar
2025-12-02 1:57 ` Eric Biggers
2025-12-02 10:14 ` Alejandro Colomar
2025-12-02 13:42 ` Alejandro Colomar
2025-12-02 16:49 ` Eric Biggers
2025-12-02 21:27 ` Alejandro Colomar
2025-12-03 17:24 ` Daniel Thompson
2025-12-03 18:01 ` Alejandro Colomar
2025-12-05 13:59 ` Daniel Thompson
2025-12-13 20:04 ` Alejandro Colomar
2025-11-16 13:57 ` kernel test robot
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=aRi6zrH3sGyTZcmf@zx2c4.com \
--to=jason@zx2c4.com \
--cc=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=ebiggers@kernel.org \
--cc=kees@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=torvalds@linux-foundation.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.