mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Benno Lossin" <lossin@kernel.org>
To: "Christian Schrefl" <chrisi.schrefl@gmail.com>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Lee Jones" <lee@kernel.org>,
	"Daniel Almeida" <daniel.almeida@collabora.com>
Cc: "Gerald Wisböck" <gerald.wisboeck@feather.ink>,
	rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 3/3] rust: miscdevice: adjust the rust_misc_device sample to use RegistrationData.
Date: Sat, 31 May 2025 14:27:52 +0200	[thread overview]
Message-ID: <DAACGEDVW8D4.66KOF7PWD1I0@kernel.org> (raw)
In-Reply-To: <20250530-b4-rust_miscdevice_registrationdata-v4-3-d313aafd7e59@gmail.com>

On Fri May 30, 2025 at 10:46 PM CEST, Christian Schrefl wrote:
> Add a second mutex to the RustMiscDevice, which is shared between all
> instances of the device using an Arc and the RegistrationData of
> MiscDeviceRegistration.
>
> This is mostly to demonstrate the capability to share data in this way.
>
> Signed-off-by: Christian Schrefl <chrisi.schrefl@gmail.com>

Two nits below, with those fixed:

Reviewed-by: Benno Lossin <lossin@kernel.org>

> @@ -94,7 +152,6 @@
>  //!   return 0;
>  //! }
>  //! ```
> -

Let's keep this newline.

>  use core::pin::Pin;
>  
>  use kernel::{

> @@ -193,7 +263,6 @@ fn ioctl(me: Pin<&RustMiscDevice>, _file: &File, cmd: u32, arg: usize) -> Result
>          Ok(0)
>      }
>  }
> -

This one too.

---
Cheers,
Benno

>  #[pinned_drop]
>  impl PinnedDrop for RustMiscDevice {
>      fn drop(self: Pin<&mut Self>) {
> @@ -204,7 +273,7 @@ fn drop(self: Pin<&mut Self>) {
>  impl RustMiscDevice {
>      fn set_value(&self, mut reader: UserSliceReader) -> Result<isize> {
>          let new_value = reader.read::<i32>()?;
> -        let mut guard = self.inner.lock();
> +        let mut guard = self.unique.lock();
>  
>          dev_info!(
>              self.dev,

  reply	other threads:[~2025-05-31 12:27 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-30 20:46 [PATCH v4 0/3] rust: miscdevice: add additional data to MiscDeviceRegistration Christian Schrefl
2025-05-30 20:46 ` [PATCH v4 1/3] rust: implement `Wrapper<T>` for `Opaque<T>` Christian Schrefl
2025-05-30 20:53   ` Christian Schrefl
2025-05-30 21:43     ` Danilo Krummrich
2025-05-30 20:46 ` [PATCH v4 2/3] rust: miscdevice: add additional data to MiscDeviceRegistration Christian Schrefl
2025-05-31 12:23   ` Benno Lossin
2025-06-02 21:16     ` Christian Schrefl
2025-06-03 23:29       ` Benno Lossin
2025-06-04  8:48         ` Miguel Ojeda
2025-06-04  9:54           ` Christian Schrefl
2025-06-04 10:13             ` Miguel Ojeda
2025-06-05 14:57         ` Christian Schrefl
2025-06-05 16:05           ` Benno Lossin
2025-06-05 16:52             ` Christian Schrefl
2025-06-05 17:27               ` Benno Lossin
2025-06-07 11:34                 ` Christian Schrefl
2025-06-07 15:37                   ` Benno Lossin
2025-06-07 15:39                     ` Christian Schrefl
2025-06-07 19:05                       ` Benno Lossin
2025-06-04  9:40       ` Alice Ryhl
2025-06-04  9:42         ` Christian Schrefl
2025-06-04  9:43           ` Alice Ryhl
2025-06-04  9:37     ` Alice Ryhl
2025-06-04  9:41       ` Alice Ryhl
2025-05-30 20:46 ` [PATCH v4 3/3] rust: miscdevice: adjust the rust_misc_device sample to use RegistrationData Christian Schrefl
2025-05-31 12:27   ` Benno Lossin [this message]
2025-05-31 13:40     ` Miguel Ojeda
2025-06-02 21:20       ` Christian Schrefl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DAACGEDVW8D4.66KOF7PWD1I0@kernel.org \
    --to=lossin@kernel.org \
    --cc=a.hindborg@kernel.org \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=arnd@arndb.de \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=chrisi.schrefl@gmail.com \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=gary@garyguo.net \
    --cc=gerald.wisboeck@feather.ink \
    --cc=gregkh@linuxfoundation.org \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tmgross@umich.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®