linux-kernel - Re: [GIT PULL] Rust pin-init for v7.0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CANiq72mb0s4_gAW2wOQ=JBcpzkLg5tHA1TQ01V9WoFUqv7Pi7A@mail.gmail.com>
Date: Wed, 28 Jan 2026 16:03:30 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Benno Lossin <lossin@...nel.org>, Gary Guo <gary@...yguo.net>
Cc: Miguel Ojeda <ojeda@...nel.org>, Boqun Feng <boqun.feng@...il.com>, 
	Björn Roy Baron <bjorn3_gh@...tonmail.com>, 
	Andreas Hindborg <a.hindborg@...nel.org>, Alice Ryhl <aliceryhl@...gle.com>, 
	Trevor Gross <tmgross@...ch.edu>, Danilo Krummrich <dakr@...nel.org>, Fiona Behrens <me@...enk.dev>, 
	Christian Schrefl <chrisi.schrefl@...il.com>, Tamir Duberstein <tamird@...il.com>, 
	Alban Kurti <kurti@...icto.ai>, linux-kernel@...r.kernel.org, 
	rust-for-linux@...r.kernel.org
Subject: Re: [GIT PULL] Rust pin-init for v7.0

On Thu, Jan 22, 2026 at 11:10 AM Benno Lossin <lossin@...nel.org> wrote:
>
> Hi Miguel,
>
> Lot's of changes in this one, mainly the `syn` rewrite, but also some
> smaller changes such as removing the `try_` versions of the macros in
> pin-init (the kernel still declares its own).
>
> All commits have been in linux-next since Monday.
>
> The first commit in my tree is also in the `syn` patch series from Gary
> [1], to avoid problems it should be merged after this tag. There also is
> a "phantom conflict" with 74e15ac34b098 ("scripts:
> generate_rust_analyzer: Add pin_init_internal deps") in rust-fixes,
> which you already saw in linux-next [2]. Otherwise no conflicts
> expected.
>
> Please pull for v7.0 -- thanks!

Merged into `rust-next` and Gary's series (without his first patch)
right after that -- thank you!

By the way, in the PR message, it would be nice if you could use the
imperative, since that is nowadays the style maintainers should use
for PRs. I reworded it a bit to conform, please take a look.

e.g. instead of "'...' now support ...", I wrote "Support ... in
'...'" (and so on).

Cheers,
Miguel