rust: kernel: allow a few non_send_fields_in_send_ty Clippy cases

Signed-off-by: Miguel Ojeda <ojeda@kernel.org>

Author: ojeda

rust/kernel/gpio.rs

@@ -218,6 +218,7 @@ unsafe impl<T: Chip> Sync for Registration<T> {}
 // SAFETY: Registration with and unregistration from the gpio subsystem can happen from any thread.
 // Additionally, `T::Data` (which is dropped during unregistration) is `Send`, so it is ok to move
 // `Registration` to different threads.
+#[allow(clippy::non_send_fields_in_send_ty)]
 unsafe impl<T: Chip> Send for Registration<T> {}
 
 impl<T: Chip> Default for Registration<T> {
@@ -399,6 +400,7 @@ mod irqchip {
     // SAFETY: Registration with and unregistration from the gpio subsystem (including irq chips for
     // them) can happen from any thread. Additionally, `T::Data` (which is dropped during
     // unregistration) is `Send`, so it is ok to move `Registration` to different threads.
+    #[allow(clippy::non_send_fields_in_send_ty)]
     unsafe impl<T: ChipWithIrqChip> Send for RegistrationWithIrqChip<T> where T::Data: Send {}
 
     struct FlowHandler<T: ChipWithIrqChip>(PhantomData<T>);

rust/kernel/sync/condvar.rs

@@ -35,6 +35,7 @@ pub struct CondVar {
 }
 
 // SAFETY: `CondVar` only uses a `struct wait_queue_head`, which is safe to use on any thread.
+#[allow(clippy::non_send_fields_in_send_ty)]
 unsafe impl Send for CondVar {}
 
 // SAFETY: `CondVar` only uses a `struct wait_queue_head`, which is safe to use on multiple threads

rust/kernel/sync/mutex.rs

@@ -40,6 +40,7 @@ pub struct Mutex<T: ?Sized> {
 }
 
 // SAFETY: `Mutex` can be transferred across thread boundaries iff the data it protects can.
+#[allow(clippy::non_send_fields_in_send_ty)]
 unsafe impl<T: ?Sized + Send> Send for Mutex<T> {}
 
 // SAFETY: `Mutex` serialises the interior mutability it provides, so it is `Sync` as long as the

rust/kernel/sync/seqlock.rs

@@ -60,6 +60,7 @@ pub struct SeqLock<L: CreatableLock + ?Sized> {
 
 // SAFETY: `SeqLock` can be transferred across thread boundaries iff the data it protects and the
 // underlying lock can.
+#[allow(clippy::non_send_fields_in_send_ty)]
 unsafe impl<L: CreatableLock + Send> Send for SeqLock<L> where L::Inner: Send {}
 
 // SAFETY: `SeqLock` allows concurrent access to the data it protects by both readers and writers,