From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Guillaume Gomez <guillaume1.gomez@gmail.com>
Cc: "Benno Lossin" <lossin@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Fiona Behrens" <me@kloenk.dev>, "Alban Kurti" <kurti@invicto.ai>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] rust: pin-init: fix broken rust doc link
Date: Wed, 19 Nov 2025 19:27:58 +0100 [thread overview]
Message-ID: <CANiq72mzOn7sHTMMODF4echBj0rGS=fsUesfeFDzLyXjj2xw=w@mail.gmail.com> (raw)
In-Reply-To: <CAAOQCfQzhxDzaJOb3GyVPgcVD0npso4bJ8zuy_63ZSr-rnQ0nA@mail.gmail.com>
On Fri, Oct 17, 2025 at 3:06 PM Guillaume Gomez
<guillaume1.gomez@gmail.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
next prev parent reply other threads:[~2025-11-19 18:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 21:17 [PATCH 1/2] rust: pin-init: fix broken rust doc link Benno Lossin
2025-10-16 21:17 ` [PATCH 2/2] rust: pin-init: fix typo in docs Benno Lossin
2025-10-16 21:24 ` [PATCH 1/2] rust: pin-init: fix broken rust doc link Miguel Ojeda
2025-10-16 21:47 ` Benno Lossin
2025-10-17 12:58 ` Miguel Ojeda
2025-10-17 13:06 ` Guillaume Gomez
2025-11-19 18:27 ` Miguel Ojeda [this message]
2025-11-19 21:20 ` Guillaume Gomez
2025-10-18 19:26 ` Miguel Ojeda
2025-11-19 21:55 ` Miguel Ojeda
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='CANiq72mzOn7sHTMMODF4echBj0rGS=fsUesfeFDzLyXjj2xw=w@mail.gmail.com' \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=guillaume1.gomez@gmail.com \
--cc=kurti@invicto.ai \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=me@kloenk.dev \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--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).