From: Andreas Hindborg <a.hindborg@kernel.org>
To: "Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
rust-for-linux@vger.kernel.org,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Bill Wendling" <morbo@google.com>,
"Justin Stitt" <justinstitt@google.com>,
llvm@lists.linux.dev, linux-kernel@vger.kernel.org,
patches@lists.linux.dev, "Aaron Ballman" <aaron@aaronballman.com>,
"Bill Wendling" <isanbard@gmail.com>,
"Cole Nixon" <nixontcole@gmail.com>,
"Connor Kuehl" <cipkuehl@gmail.com>,
"Fangrui Song" <i@maskray.me>,
"James Foster" <jafosterja@gmail.com>,
"Jeff Takahashi" <jeffrey.takahashi@gmail.com>,
"Jordan Cantrell" <jordan.cantrell@mail.com>,
"Matthew Maurer" <mmaurer@google.com>,
"Nikk Forbus" <nicholas.forbus@gmail.com>,
"Qing Zhao" <qing.zhao@oracle.com>,
"Sami Tolvanen" <samitolvanen@google.com>,
"Tim Pugh" <nwtpugh@gmail.com>, "Kees Cook" <kees@kernel.org>,
"Nicolas Schier" <n.schier@avm.de>
Subject: Re: [RFC PATCH] rust: allow Clang-native `RANDSTRUCT` configs
Date: Tue, 29 Apr 2025 15:40:43 +0200 [thread overview]
Message-ID: <87jz732ihw.fsf@kernel.org> (raw)
In-Reply-To: <CANiq72mNJrMMbEcfJMLT4kM-_iviM0AR6oeigCyrb5eMWkn3KQ@mail.gmail.com> (Miguel Ojeda's message of "Tue, 29 Apr 2025 15:19:13 +0200")
"Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com> writes:
> On Thu, Jan 9, 2025 at 3:51 PM Miguel Ojeda
> <miguel.ojeda.sandonis@gmail.com> wrote:
>>
>> I may pick this very early next cycle so that we can get some testing
>> during the -rc's, and just drop it if something breaks for anyone.
>>
>> But any other testing beforehand would be still very welcome...
>
> I ended up waiting on this one since I think Andreas would be able to
> try it with some actual workload (the nice benchmarks he has). Anyway,
> it will go in sooner or later.
It is on my list, sorry for not getting to that yet.
Best regards,
Andreas Hindborg
next prev parent reply other threads:[~2025-04-29 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 18:57 [RFC PATCH] rust: allow Clang-native `RANDSTRUCT` configs Miguel Ojeda
2025-01-09 14:51 ` Miguel Ojeda
2025-04-29 13:19 ` Miguel Ojeda
2025-04-29 13:40 ` Andreas Hindborg [this message]
2025-04-29 13:48 ` Miguel Ojeda
2025-12-10 7:21 ` 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=87jz732ihw.fsf@kernel.org \
--to=a.hindborg@kernel.org \
--cc=aaron@aaronballman.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=cipkuehl@gmail.com \
--cc=gary@garyguo.net \
--cc=i@maskray.me \
--cc=isanbard@gmail.com \
--cc=jafosterja@gmail.com \
--cc=jeffrey.takahashi@gmail.com \
--cc=jordan.cantrell@mail.com \
--cc=justinstitt@google.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mmaurer@google.com \
--cc=morbo@google.com \
--cc=n.schier@avm.de \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicholas.forbus@gmail.com \
--cc=nixontcole@gmail.com \
--cc=nwtpugh@gmail.com \
--cc=ojeda@kernel.org \
--cc=patches@lists.linux.dev \
--cc=qing.zhao@oracle.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=samitolvanen@google.com \
--cc=tmgross@umich.edu \
/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).