[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAOQCfSFQCvca=9-nspsxg70W4vXk66sxUixH9c=R71PZHSzQQ@mail.gmail.com>
Date: Wed, 19 Nov 2025 22:20:01 +0100
From: Guillaume Gomez <guillaume1.gomez@...il.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: Benno Lossin <lossin@...nel.org>, Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>, Boqun Feng <boqun.feng@...il.com>,
Gary Guo <gary@...yguo.net>, 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>,
Alban Kurti <kurti@...icto.ai>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] rust: pin-init: fix broken rust doc link
Thanks for opening them!
Gonna take a look tomorrow.
Le mer. 19 nov. 2025 à 19:28, Miguel Ojeda
<miguel.ojeda.sandonis@...il.com> a écrit :
>
> On Fri, Oct 17, 2025 at 3:06 PM Guillaume Gomez
> <guillaume1.gomez@...il.com> wrote:
> >
> > Indeed, although, please open an issue on rust repository so the team
> > can discuss how this feature would look like.
>
> Done -- for both the features (checking & runtime toggle):
>
> https://github.com/rust-lang/rust/issues/149105
> https://github.com/rust-lang/rust/issues/149106
>
> Of course, if we have the latter, then we may not need the former etc.
> I tried to add a good chunk of context in the issues, especially the
> first one.
>
> I hope that helps, and thanks Guillaume!
>
> Cheers,
> Miguel
Powered by blists - more mailing lists