From: "Danilo Krummrich" <dakr@kernel.org>
To: "Alistair Popple" <apopple@nvidia.com>
Cc: rust-for-linux@vger.kernel.org,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"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" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"John Hubbard" <jhubbard@nvidia.com>,
"Alexandre Courbot" <acourbot@nvidia.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] rust: Add several miscellaneous PCI helpers
Date: Tue, 08 Jul 2025 11:32:24 +0200 [thread overview]
Message-ID: <DB6KIR4X6GKM.3EJYQJXILGOGN@kernel.org> (raw)
In-Reply-To: <20250708060451.398323-2-apopple@nvidia.com>
On Tue Jul 8, 2025 at 8:04 AM CEST, Alistair Popple wrote:
> diff --git a/rust/kernel/pci.rs b/rust/kernel/pci.rs
> index 7f640ba8f19c..f41fd9facb90 100644
> --- a/rust/kernel/pci.rs
> +++ b/rust/kernel/pci.rs
> @@ -393,6 +393,42 @@ pub fn device_id(&self) -> u16 {
> unsafe { (*self.as_raw()).device }
> }
>
> + /// Returns the PCI revision ID.
> + pub fn revision_id(&self) -> u8 {
We should add a compiler hint for those methods to be inlined.
> + // SAFETY: `self.as_raw` is a valid pointer to a `struct pci_dev`.
Let's refer to the type invariant for the validity of self.as_raw().
> + unsafe { (*self.as_raw()).revision }
> + }
Both is also true for the existing methods vendor_id() and device_id(). Can you
please fix them up in a separate patch as well?
Also, please add a brief note in the commit message where those will be used
(even though I obviously know). :)
next prev parent reply other threads:[~2025-07-08 9:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 6:04 [PATCH 1/2] rust: Add dma_set_mask() and dma_set_coherent_mask() bindings Alistair Popple
2025-07-08 6:04 ` [PATCH 2/2] rust: Add several miscellaneous PCI helpers Alistair Popple
2025-07-08 7:05 ` Alexandre Courbot
2025-07-08 8:07 ` Greg Kroah-Hartman
2025-07-09 1:50 ` Alistair Popple
2025-07-08 9:32 ` Danilo Krummrich [this message]
2025-07-09 1:43 ` Alistair Popple
2025-07-08 7:01 ` [PATCH 1/2] rust: Add dma_set_mask() and dma_set_coherent_mask() bindings Alexandre Courbot
2025-07-08 8:07 ` Alistair Popple
2025-07-08 8:40 ` Danilo Krummrich
2025-07-08 9:48 ` Danilo Krummrich
2025-07-08 20:44 ` Danilo Krummrich
2025-07-09 1:41 ` Alistair Popple
2025-07-10 19:39 ` 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=DB6KIR4X6GKM.3EJYQJXILGOGN@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=apopple@nvidia.com \
--cc=bhelgaas@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=jhubbard@nvidia.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lossin@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 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).