From: John Hubbard <jhubbard@nvidia.com>
To: Alexandre Courbot <acourbot@nvidia.com>,
Danilo Krummrich <dakr@kernel.org>
Cc: "Joel Fernandes" <joelagnelf@nvidia.com>,
"Timur Tabi" <ttabi@nvidia.com>,
"Alistair Popple" <apopple@nvidia.com>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"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>,
nouveau@lists.freedesktop.org, linux-pci@vger.kernel.org,
rust-for-linux@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] rust: pci: display symbolic PCI vendor and class names
Date: Thu, 25 Sep 2025 16:27:08 -0700 [thread overview]
Message-ID: <142cd07d-c251-463a-83b2-246d6af278d1@nvidia.com> (raw)
In-Reply-To: <DD1JORQ8539K.1H5X1SIF7J3WD@nvidia.com>
On 9/24/25 8:01 PM, Alexandre Courbot wrote:
> On Thu Sep 25, 2025 at 10:33 AM JST, John Hubbard wrote:
>> Hi,
>>
>> This applies to:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git
>>
>> It's a small follow up to these commits in that same branch:
>>
>> commit 5e20962a9fc8 ("rust: pci: provide access to PCI Vendor values")
>> commit ed78a01887e2 ("rust: pci: provide access to PCI Class and Class-related items")
>>
>> Danilo, I've added your Suggested-by to these.
>>
>> John Hubbard (2):
>> rust: pci: display symbolic PCI class names
>> rust: pci: display symbolic PCI vendor names
>>
>> rust/kernel/pci/id.rs | 36 +++++++++++++++++++++++-------------
>> 1 file changed, 23 insertions(+), 13 deletions(-)
>
> The series,
>
> Reviewed-by: Alexandre Courbot <acourbot@nvidia.com>
Thanks for the review, Alex!
thanks,
--
John Hubbard
next prev parent reply other threads:[~2025-09-25 23:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 1:33 [PATCH 0/2] rust: pci: display symbolic PCI vendor and class names John Hubbard
2025-09-25 1:33 ` [PATCH 1/2] rust: pci: display symbolic PCI " John Hubbard
2025-09-25 1:33 ` [PATCH 2/2] rust: pci: display symbolic PCI vendor names John Hubbard
2025-09-25 1:38 ` John Hubbard
2025-09-25 3:01 ` [PATCH 0/2] rust: pci: display symbolic PCI vendor and class names Alexandre Courbot
2025-09-25 23:27 ` John Hubbard [this message]
2025-09-25 16:04 ` Danilo Krummrich
2025-09-25 23:28 ` John Hubbard
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=142cd07d-c251-463a-83b2-246d6af278d1@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.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=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=joelagnelf@nvidia.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=tmgross@umich.edu \
--cc=ttabi@nvidia.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