rust: kernel: fix typos in code comments

//!         }

//!     }

//!     // Implement the internal `PinData` trait that marks the pin-data struct as a pin-data

//!     // struct. This is important to ensure that no user can implement a rouge `__pin_data`

//!     // struct. This is important to ensure that no user can implement a rogue `__pin_data`

//!     // function without using `unsafe`.

//!     unsafe impl<T> ::kernel::init::__internal::PinData for __ThePinData<T> {

//!         type Datee = Bar<T>;

//!     // case no such fields exist, hence this is almost empty. The two phantomdata fields exist

//!     // for two reasons:

//!     // - `__phantom`: every generic must be used, since we cannot really know which generics

//!     //   are used, we declere all and then use everything here once.

//!     //   are used, we declare all and then use everything here once.

//!     // - `__phantom_pin`: uses the `'__pin` lifetime and ensures that this struct is invariant

//!     //   over it. The lifetime is needed to work around the limitation that trait bounds must

//!     //   not be trivial, e.g. the user has a `#[pin] PhantomPinned` field -- this is

pub struct DriverVTable(Opaque<bindings::phy_driver>);

// SAFETY: `DriverVTable` doesn't expose any &self method to access internal data, so it's safe to

// share `&DriverVTable` across execution context boundries.

// share `&DriverVTable` across execution context boundaries.

unsafe impl Sync for DriverVTable {}

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