mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git
synced 2026-04-21 04:53:46 -04:00
rust: types: add intra-doc links for Opaque<T>
We use intra-doc links wherever possible. Thus add a couple missing ones for `Opaque<T>`. Signed-off-by: Dirk Behme <dirk.behme@de.bosch.com> Reviewed-by: Alice Ryhl <aliceryhl@google.com> Reviewed-by: Fiona Behrens <me@kloenk.dev> Reviewed-by: Andreas Hindborg <a.hindborg@kernel.org> Link: https://lore.kernel.org/r/20250305053438.1532397-1-dirk.behme@de.bosch.com [ Reworded. - Miguel ] Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
This commit is contained in:
@@ -251,7 +251,7 @@ impl<T, F: FnOnce(T)> Drop for ScopeGuard<T, F> {
|
||||
|
||||
/// Stores an opaque value.
|
||||
///
|
||||
/// `Opaque<T>` is meant to be used with FFI objects that are never interpreted by Rust code.
|
||||
/// [`Opaque<T>`] 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<bindings::mutex>`.
|
||||
/// It gets rid of all the usual assumptions that Rust has for a value:
|
||||
@@ -266,7 +266,7 @@ impl<T, F: FnOnce(T)> Drop for ScopeGuard<T, F> {
|
||||
/// 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<T>` allows to continue to use references on the Rust side even for values shared
|
||||
/// Using [`Opaque<T>`] allows to continue to use references on the Rust side even for values shared
|
||||
/// with C.
|
||||
///
|
||||
/// # Examples
|
||||
|
||||
Reference in New Issue
Block a user