From: Danilo Krummrich <dakr@kernel.org>
To: gregkh@linuxfoundation.org, rafael@kernel.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,
bhelgaas@google.com, fujita.tomonori@gmail.com
Cc: linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
linux-pci@vger.kernel.org, Danilo Krummrich <dakr@kernel.org>
Subject: [PATCH 0/3] Fixes for Rust Device / Driver abstractions
Date: Fri, 3 Jan 2025 17:46:00 +0100 [thread overview]
Message-ID: <20250103164655.96590-1-dakr@kernel.org> (raw)
This patch series contains a few fixes for the preceding series [1] introducing
device / driver Rust abstractions.
Except for the CONFIG_PCI_MSI dependency fix, there's no functional change.
[1] https://lore.kernel.org/rust-for-linux/20241219170425.12036-1-dakr@kernel.org/
Danilo Krummrich (3):
rust: pci: do not depend on CONFIG_PCI_MSI
rust: io: move module entry to its correct location
rust: driver: address soundness issue in `RegistrationOps`
rust/kernel/driver.rs | 25 ++++++++++++++++++++-----
rust/kernel/lib.rs | 6 +++---
rust/kernel/pci.rs | 8 +++++---
rust/kernel/platform.rs | 8 +++++---
4 files changed, 33 insertions(+), 14 deletions(-)
base-commit: 06e843bbbf2107463249ea6f6b1a736f5647e24a
prerequisite-patch-id: 5ce64efa11560206236db2b2f014ceaa3d2e9fa3
prerequisite-patch-id: e86a1e93ce4e9e8440be0bb641ef99def521b75f
--
2.47.1
next reply other threads:[~2025-01-03 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 16:46 Danilo Krummrich [this message]
2025-01-03 16:46 ` [PATCH 1/3] rust: pci: do not depend on CONFIG_PCI_MSI Danilo Krummrich
2025-01-07 10:31 ` Greg KH
2025-01-07 10:41 ` Danilo Krummrich
2025-01-03 16:46 ` [PATCH 2/3] rust: io: move module entry to its correct location Danilo Krummrich
2025-01-03 16:46 ` [PATCH 3/3] rust: driver: address soundness issue in `RegistrationOps` Danilo Krummrich
2025-01-05 19:07 ` Gary Guo
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=20250103164655.96590-1-dakr@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bhelgaas@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rafael@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.