File tree 2 files changed +3
-3
lines changed
2 files changed +3
-3
lines changed Original file line number Diff line number Diff line change 145
145
//! }
146
146
//! }
147
147
//! // Implement the internal `PinData` trait that marks the pin-data struct as a pin-data
148
- //! // struct. This is important to ensure that no user can implement a rouge `__pin_data`
148
+ //! // struct. This is important to ensure that no user can implement a rogue `__pin_data`
149
149
//! // function without using `unsafe`.
150
150
//! unsafe impl<T> ::kernel::init::__internal::PinData for __ThePinData<T> {
151
151
//! type Datee = Bar<T>;
156
156
//! // case no such fields exist, hence this is almost empty. The two phantomdata fields exist
157
157
//! // for two reasons:
158
158
//! // - `__phantom`: every generic must be used, since we cannot really know which generics
159
- //! // are used, we declere all and then use everything here once.
159
+ //! // are used, we declare all and then use everything here once.
160
160
//! // - `__phantom_pin`: uses the `'__pin` lifetime and ensures that this struct is invariant
161
161
//! // over it. The lifetime is needed to work around the limitation that trait bounds must
162
162
//! // not be trivial, e.g. the user has a `#[pin] PhantomPinned` field -- this is
Original file line number Diff line number Diff line change @@ -491,7 +491,7 @@ impl<T: Driver> Adapter<T> {
491
491
pub struct DriverVTable ( Opaque < bindings:: phy_driver > ) ;
492
492
493
493
// SAFETY: `DriverVTable` doesn't expose any &self method to access internal data, so it's safe to
494
- // share `&DriverVTable` across execution context boundries .
494
+ // share `&DriverVTable` across execution context boundaries .
495
495
unsafe impl Sync for DriverVTable { }
496
496
497
497
/// Creates a [`DriverVTable`] instance from [`Driver`].
You can’t perform that action at this time.
0 commit comments