From: Dirk Behme Date: Wed, 5 Mar 2025 05:34:37 +0000 (+0100) Subject: rust: types: add intra-doc links for `Opaque` X-Git-Tag: v6.15-rc1~93^2~43 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=ab2ebb7bc9d9af2f50b0ad54deb65e1d0b01bc70;p=thirdparty%2Fkernel%2Flinux.git rust: types: add intra-doc links for `Opaque` We use intra-doc links wherever possible. Thus add a couple missing ones for `Opaque`. Signed-off-by: Dirk Behme Reviewed-by: Alice Ryhl Reviewed-by: Fiona Behrens Reviewed-by: Andreas Hindborg Link: https://lore.kernel.org/r/20250305053438.1532397-1-dirk.behme@de.bosch.com [ Reworded. - Miguel ] Signed-off-by: Miguel Ojeda --- diff --git a/rust/kernel/types.rs b/rust/kernel/types.rs index 9cb573d39c349..5801eeb69dc5e 100644 --- a/rust/kernel/types.rs +++ b/rust/kernel/types.rs @@ -251,7 +251,7 @@ impl Drop for ScopeGuard { /// Stores an opaque value. /// -/// `Opaque` is meant to be used with FFI objects that are never interpreted by Rust code. +/// [`Opaque`] is meant to be used with FFI objects that are never interpreted by Rust code. /// /// It is used to wrap structs from the C side, like for example `Opaque`. /// It gets rid of all the usual assumptions that Rust has for a value: @@ -266,7 +266,7 @@ impl Drop for ScopeGuard { /// This has to be used for all values that the C side has access to, because it can't be ensured /// that the C side is adhering to the usual constraints that Rust needs. /// -/// Using `Opaque` allows to continue to use references on the Rust side even for values shared +/// Using [`Opaque`] allows to continue to use references on the Rust side even for values shared /// with C. /// /// # Examples