public inbox for rust-for-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Guangbo Cui <2407018371@qq.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Miguel Ojeda" <ojeda@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>,
	"Benno Lossin" <benno.lossin@proton.me>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Trevor Gross" <tmgross@umich.edu>,
	rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] Add UIO (Userspace I/O) device rust abstraction
Date: Wed, 11 Dec 2024 21:57:42 +0800	[thread overview]
Message-ID: <tencent_C3D31BDA67AD3F485B2E4D3498E930CD9F09@qq.com> (raw)
In-Reply-To: <2024121150-stretch-password-2179@gregkh>

> Very cool!  But can we also see this with a "real" UIO driver as well?

Sure, I will look for a suitable UIO driver to start with. I’ve been quite
busy recently and might not have enough time to dedicate to it, but I will
continue working on it.

> Heck, even a conversion of something "simple" like the uio_dfl.c or
> uio_cif.c would be nice to see (you have to do this on top of the
> platform or pci rust bindings, see the list for the most recent round of
> them).  Seeing how this will be used is kind of key to ensure that we
> know the bindings work properly.

Yes, this patch is on the top of the latest platform rust bindings. 

Best regards,
Guangbo Cui


      reply	other threads:[~2024-12-11 14:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11 12:43 [RFC PATCH] Add UIO (Userspace I/O) device rust abstraction Guangbo Cui
2024-12-11 13:26 ` Greg Kroah-Hartman
2024-12-11 13:57   ` Guangbo Cui [this message]

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=tencent_C3D31BDA67AD3F485B2E4D3498E930CD9F09@qq.com \
    --to=2407018371@qq.com \
    --cc=a.hindborg@kernel.org \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=benno.lossin@proton.me \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dakr@kernel.org \
    --cc=gary@garyguo.net \
    --cc=gregkh@linuxfoundation.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