[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <878qpjg6sj.fsf@kernel.org>
Date: Wed, 05 Mar 2025 10:34:20 +0100
From: Andreas Hindborg <a.hindborg@...nel.org>
To: "Benno Lossin" <benno.lossin@...ton.me>
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>, "Alice
Ryhl" <aliceryhl@...gle.com>, "Trevor Gross" <tmgross@...ch.edu>,
"Danilo Krummrich" <dakr@...nel.org>, <rust-for-linux@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 04/22] rust: pin-init: move proc-macro documentation
into pin-init crate
"Benno Lossin" <benno.lossin@...ton.me> writes:
> Move the documentation of proc-macros from pin-init-internal into
> pin-init. This is because documentation can only reference types from
> dependencies and pin-init-internal cannot have pin-init as a dependency,
> as that would be cyclic.
`pin_data` et. al. is now re-exported both in `kernel::prelude` and
`kernel::init`, but I guess that is fine?
When you say "can only reference types", do you mean via links in the text?
Best regards,
Andreas Hindborg
Powered by blists - more mailing lists