Lines Matching refs:Rust

6 This document describes how to write Rust code in the kernel.
21 The default settings of ``rustfmt`` are used. This means the idiomatic Rust
27 the entire kernel Rust sources is needed at some point, the following can be
195 Rust kernel code is not documented like C kernel code (i.e. via kernel-doc).
196 Instead, the usual system for documenting Rust code is used: the ``rustdoc``
204 This is how a well-documented Rust function may look like:
251 - Rust items (functions, types, constants...) must be linked appropriately
262 To learn more about how to write documentation for Rust and extra features,
284 Rust kernel code refers to C types, such as ``int``, using type aliases such as
301 Rust kernel code follows the usual Rust naming conventions:
306 a Rust abstraction, a name as close as reasonably possible to the C side should
308 back and forth between the C and Rust sides. For instance, macros such as
309 ``pr_info`` from C are named the same in the Rust side.
311 Having said that, casing should be adjusted to follow the Rust naming
320 The equivalent in Rust may look like (ignoring documentation):
339 In Rust, it is possible to ``allow`` particular warnings (diagnostics, lints)
355        is meant to reflect the equivalent lint in Rust discussed afterwards.
369 On top of that, Rust provides the ``expect`` attribute which takes this further.
477 For more information about diagnostics in Rust, please see:
484 For some background and guidelines about Rust for Linux specific error handling,