[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72=Qh9sJLKwACr_McnbGdu8JfzqDuv1AgCjSdwKtt-9Gdw@mail.gmail.com>
Date: Fri, 17 Oct 2025 14:58:49 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Benno Lossin <lossin@...nel.org>
Cc: 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, Guillaume Gomez <guillaume1.gomez@...il.com>
Subject: Re: [PATCH 1/2] rust: pin-init: fix broken rust doc link
On Thu, Oct 16, 2025 at 11:47 PM Benno Lossin <lossin@...nel.org> wrote:
>
> Thanks a lot for the added context! I will add it when applying. The
> `__pinned_drop!` macro will be gone with the syn patches this cycle, so
> in this case, we don't care what the resolution will be.
In the end, it wasn't intentional, so Guillaume created this PR:
https://github.com/rust-lang/rust/pull/147809
Thus 1.92 may end up without this change in behavior.
Guillaume and I also discussed the possibility of checking these
things nevertheless (i.e. without needing a second pass) as well as
the related topic of having a runtime solution for toggling
private/hidden items (and thus getting them checked too). We could
perhaps try a custom thing in rust.docs.kernel.org to see how it looks
and if people like it.
Cheers,
Miguel
Powered by blists - more mailing lists