Skip to content

Commit 0ff8f3f

Browse files
jubalhojeda
authored andcommitted
rust: kernel: fix typos in code comments
Fix spelling mistakes in code comments. Signed-off-by: Michael Vetter <[email protected]> Reviewed-by: Alice Ryhl <[email protected]> Reviewed-by: Benno Lossin <[email protected]> Link: https://lore.kernel.org/r/[email protected] [ Reworded slightly. - Miguel ] Signed-off-by: Miguel Ojeda <[email protected]>
1 parent 5d88f98 commit 0ff8f3f

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

Diff for: rust/kernel/init/macros.rs

+2-2
Original file line numberDiff line numberDiff line change
@@ -145,7 +145,7 @@
145145
//! }
146146
//! }
147147
//! // 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`
149149
//! // function without using `unsafe`.
150150
//! unsafe impl<T> ::kernel::init::__internal::PinData for __ThePinData<T> {
151151
//! type Datee = Bar<T>;
@@ -156,7 +156,7 @@
156156
//! // case no such fields exist, hence this is almost empty. The two phantomdata fields exist
157157
//! // for two reasons:
158158
//! // - `__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.
160160
//! // - `__phantom_pin`: uses the `'__pin` lifetime and ensures that this struct is invariant
161161
//! // over it. The lifetime is needed to work around the limitation that trait bounds must
162162
//! // not be trivial, e.g. the user has a `#[pin] PhantomPinned` field -- this is

Diff for: rust/kernel/net/phy.rs

+1-1
Original file line numberDiff line numberDiff line change
@@ -491,7 +491,7 @@ impl<T: Driver> Adapter<T> {
491491
pub struct DriverVTable(Opaque<bindings::phy_driver>);
492492

493493
// 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.
495495
unsafe impl Sync for DriverVTable {}
496496

497497
/// Creates a [`DriverVTable`] instance from [`Driver`].

0 commit comments

Comments
 (0)