Searched refs:of (Results 1 – 8 of 8) sorted by relevance
| /rust/kernel/ |
| A D | of.rs | 40 let mut of: bindings::of_device_id = unsafe { core::mem::zeroed() }; in new() variables
45 of.compatible[i] = src[i]; in new()
49 Self(of) in new()
58 $crate::of::DeviceId,
|
| A D | driver.rs | 9 use crate::{acpi, device, of, str::CStr, try_pin_init, types::Opaque, ThisModule};
179 fn of_id_table() -> Option<of::IdTable<Self::IdInfo>>; in of_id_table()
205 let id = unsafe { &*raw_id.cast::<of::DeviceId>() }; in of_id_info()
208 table.info(<of::DeviceId as crate::device_id::RawDeviceIdIndex>::index( in of_id_info()
|
| A D | platform.rs | 13 of,
102 fn of_id_table() -> Option<of::IdTable<Self::IdInfo>> { in of_id_table()
183 const OF_ID_TABLE: Option<of::IdTable<Self::IdInfo>> = None;
|
| A D | opp.rs | 606 of: bool, field
633 of: false, in from_raw_table()
651 of: false, in from_dev()
669 table.of = true; in from_of()
991 if self.of { in drop()
|
| A D | lib.rs | 103 pub mod of; module
|
| /rust/pin-init/ |
| A D | CONTRIBUTING.md | 13 For any type of bug report, please submit an issue using the bug report issue template.
24 You can ask questions in the Discussions page of the GitHub repository. If you're encountering
35 rest of this document will also cover some of the rules listed there and additional ones.
40 a CI with lots of tests not present in the kernel. However, patches are also accepted (though not
53 when fixing typos, create a single commit that fixes all of them instead of one commit per typo.
58 Certificate of Origin]. This has to be done for both mailing list submissions as well as GitHub
61 …loper's Certificate of Origin]: https://docs.kernel.org/process/submitting-patches.html#sign-your-…
70 Some of these rules can be ignored if the change is done solely to files that are not present in the
71 kernel version of this library. Those files are documented in the `sync-kernel.sh` script at the
|
| A D | README.md | 13 [Pinning][pinning] is Rust's way of ensuring data does not move.
15 It also allows in-place initialization of big `struct`s that would otherwise produce a stack
23 Another reason would be that you need the address of the object to initialize it. This stands
24 in direct conflict with Rust's normal process of first initializing an object and then moving
67 Throughout the examples we will often make use of the `CMutex` type which can be found in
68 `../examples/mutex.rs`. It is essentially a userland rebuild of the `struct mutex` type from
78 that you need to write `<-` instead of `:` for fields that you want to initialize in-place.
96 `foo` now is of the type [`impl PinInit<Foo>`]. We can now use any smart pointer that we like
134 ### Manual creation of an initializer
145 - you may assume that `slot` will stay pinned even after the closure returns until `drop` of
[all …]
|
| /rust/ |
| A D | bindgen_parameters | 3 # We want to map these types to `isize`/`usize` manually, instead of
35 # recognized, block generation of the non-helper constants.
|
Completed in 11 milliseconds