From: ManeraKai <manerakai@protonmail.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "aliceryhl@google.com" <aliceryhl@google.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"rust-for-linux@vger.kernel.org" <rust-for-linux@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] rust: miscdevice: Implemented `read` and `write`
Date: Thu, 18 Sep 2025 15:57:15 +0000 [thread overview]
Message-ID: <5cf242fd-ded4-4aea-a5b7-9c856f75fdb6@protonmail.com> (raw)
In-Reply-To: <2025091841-remindful-manned-a57f@gregkh>
> What type of real misc driver do you want to write in rust that you
> need a read/write callback and not just an ioctl one?
I don't have one in mind. I was reading your book and experimenting with
char drivers. However, I found out that you prefer new developers to use
misc instead:
https://lore.kernel.org/rust-for-linux/2024101256-amplifier-joylessly-6ca9@gregkh/
So, I wanted to safe-wrap misc for new Rust developers (me included).
And go from there to write real drivers.
next prev parent reply other threads:[~2025-09-18 15:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 14:44 [PATCH 0/3] rust: miscdevice: Extending the abstraction ManeraKai
2025-09-18 14:45 ` [PATCH 1/3] rust: miscdevice: Moved `MiscDevice` to a more general abstraction ManeraKai
2025-09-18 15:00 ` gregkh
2025-09-18 14:45 ` [PATCH 2/3] rust: miscdevice: Implemented `read` and `write` ManeraKai
2025-09-18 14:59 ` gregkh
2025-09-18 15:06 ` gregkh
2025-09-18 15:57 ` ManeraKai [this message]
2025-09-18 15:15 ` Alice Ryhl
2025-09-18 17:22 ` ManeraKai
2025-09-18 17:24 ` Alice Ryhl
2025-09-18 14:45 ` [PATCH 3/3] samples: rust: Updated the example using the Rust MiscDevice abstraction ManeraKai
2025-09-18 15:01 ` gregkh
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=5cf242fd-ded4-4aea-a5b7-9c856f75fdb6@protonmail.com \
--to=manerakai@protonmail.com \
--cc=aliceryhl@google.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rust-for-linux@vger.kernel.org \
/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).