From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Lyude Paul" <lyude@redhat.com>,
rust-for-linux@vger.kernel.org,
"Maíra Canal" <mairacanal@riseup.net>,
"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>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Mika Westerberg" <mika.westerberg@linux.intel.com>,
"Xiangfei Ding" <dingxiangfei2009@gmail.com>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] rust/kernel: Add faux device bindings
Date: Fri, 7 Feb 2025 13:16:01 +0100 [thread overview]
Message-ID: <2025020715-subsonic-silenced-36c5@gregkh> (raw)
In-Reply-To: <CANiq72=bspqRga-hTTb3Vh9kD0ctyTehM9dvJdR=8biTE+iCQw@mail.gmail.com>
On Fri, Feb 07, 2025 at 12:42:41PM +0100, Miguel Ojeda wrote:
> On Fri, Feb 7, 2025 at 1:42 AM Lyude Paul <lyude@redhat.com> wrote:
> >
> > This introduces a crate for working with faux devices in rust, along with
>
> s/crate/module
>
> (also in the module description)
>
> > +//! C header: [`include/linux/device/faux.h`]
> > +use crate::{bindings, device, error::code::*, prelude::*};
>
> Newline between.
>
> > + // SAFETY: self.0 is a valid registered faux_device via our type invariants.
>
> Markdown.
>
> > +// SAFETY: The faux device API is thread-safe
> > +unsafe impl Send for Registration {}
> > +
> > +// SAFETY: The faux device API is thread-safe
> > +unsafe impl Sync for Registration {}
>
> Perhaps some extra notes here would be useful, e.g. is it documented
> to be so? Especially since faux is being added now, it may make sense
> to e.g. take the chance to work on mentioning this on the C side.
How can or should I mention this on the C side?
thanks,
greg k-h
next prev parent reply other threads:[~2025-02-07 12:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 0:40 [PATCH v2] rust/kernel: Add faux device bindings Lyude Paul
2025-02-07 9:25 ` Greg Kroah-Hartman
2025-02-07 9:32 ` Alice Ryhl
2025-02-07 15:22 ` Greg Kroah-Hartman
2025-02-07 12:17 ` Danilo Krummrich
2025-02-07 15:15 ` Greg Kroah-Hartman
2025-02-07 11:42 ` Miguel Ojeda
2025-02-07 12:16 ` Greg Kroah-Hartman [this message]
2025-02-07 22:10 ` Lyude Paul
2025-02-09 11:10 ` Miguel Ojeda
2025-02-09 15:43 ` Greg Kroah-Hartman
2025-02-09 23:04 ` Benno Lossin
2025-02-07 22:29 ` Lyude Paul
2025-02-09 11:11 ` Miguel Ojeda
2025-02-07 18:17 ` Danilo Krummrich
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=2025020715-subsonic-silenced-36c5@gregkh \
--to=gregkh@linuxfoundation.org \
--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=dingxiangfei2009@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=mairacanal@riseup.net \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mika.westerberg@linux.intel.com \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=wedsonaf@gmail.com \
/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