From: Danilo Krummrich <dakr@kernel.org>
To: Lee Jones <lee@kernel.org>
Cc: linux-kernel@vger.kernel.org, arnd@arndb.de,
gregkh@linuxfoundation.org, ojeda@kernel.org,
alex.gaynor@gmail.com, boqun.feng@gmail.com, gary@garyguo.net,
bjorn3_gh@protonmail.com, benno.lossin@proton.me,
a.hindborg@kernel.org, aliceryhl@google.com, tmgross@umich.edu,
rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v5 0/4] rust: miscdevice: Provide sample driver using the new MiscDevice bindings
Date: Fri, 6 Dec 2024 13:51:04 +0100 [thread overview]
Message-ID: <Z1LzOORuFpO0MXAZ@pollux> (raw)
In-Reply-To: <20241206124218.165880-1-lee@kernel.org>
On Fri, Dec 06, 2024 at 12:42:11PM +0000, Lee Jones wrote:
> It has been suggested that the driver should use dev_info() instead of
> pr_info() however there is currently no scaffolding to successfully pull
> a 'struct device' out from driver data post register(). This is being
> worked on and we will convert this over in due course.
I think you're going too fast with this series.
Please address the comments you receive before sending out new versions.
Also, please document the changes you have made from one version to the next,
otherwise it's gonna be very hard to review this.
Thanks,
Danilo
>
> Lee Jones (4):
> Documentation: ioctl-number: Carve out some identifiers for use by
> sample drivers
> samples: rust: Provide example using the new Rust MiscDevice
> abstraction
> sample: rust_misc_device: Demonstrate additional get/set value
> functionality
> MAINTAINERS: Add Rust Misc Sample to MISC entry
>
> .../userspace-api/ioctl/ioctl-number.rst | 1 +
> MAINTAINERS | 1 +
> samples/rust/Kconfig | 10 ++
> samples/rust/Makefile | 1 +
> samples/rust/rust_misc_device.rs | 132 ++++++++++++++++++
> 5 files changed, 145 insertions(+)
> create mode 100644 samples/rust/rust_misc_device.rs
>
> --
> 2.47.0.338.g60cca15819-goog
>
>
next prev parent reply other threads:[~2024-12-06 12:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 12:42 [PATCH v5 0/4] rust: miscdevice: Provide sample driver using the new MiscDevice bindings Lee Jones
2024-12-06 12:42 ` [PATCH v5 1/4] Documentation: ioctl-number: Carve out some identifiers for use by sample drivers Lee Jones
2024-12-06 12:42 ` [PATCH v5 2/4] samples: rust: Provide example using the new Rust MiscDevice abstraction Lee Jones
2024-12-06 12:42 ` [PATCH v5 3/4] sample: rust_misc_device: Demonstrate additional get/set value functionality Lee Jones
2024-12-06 12:59 ` Greg KH
2024-12-06 13:04 ` Lee Jones
2024-12-06 13:06 ` Lee Jones
2024-12-06 13:10 ` Greg KH
2024-12-06 13:17 ` Lee Jones
2024-12-06 12:42 ` [PATCH v5 4/4] MAINTAINERS: Add Rust Misc Sample to MISC entry Lee Jones
2024-12-06 12:51 ` Danilo Krummrich [this message]
2024-12-06 12:54 ` [PATCH v5 0/4] rust: miscdevice: Provide sample driver using the new MiscDevice bindings Lee Jones
2024-12-06 13:05 ` Danilo Krummrich
2024-12-06 13:14 ` Lee Jones
2024-12-06 13:34 ` Danilo Krummrich
2024-12-06 16:49 ` Lee Jones
2024-12-06 18:29 ` Danilo Krummrich
2024-12-06 22:06 ` Lee Jones
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=Z1LzOORuFpO0MXAZ@pollux \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=arnd@arndb.de \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--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;
as well as URLs for NNTP newsgroup(s).