From: Danilo Krummrich <dakr@kernel.org>
To: Rahul Rameshbabu <sergeantsagara@protonmail.com>
Cc: rust-for-linux@vger.kernel.org, linux-pci@vger.kernel.org,
alex.gaynor@gmail.com, bhelgaas@google.com,
kwilczynski@kernel.org, ojeda@kernel.org, wt@penguintechs.org
Subject: Re: [PATCH v2] rust: pci: fix documentation related to Device instances
Date: Mon, 7 Jul 2025 14:44:14 +0200 [thread overview]
Message-ID: <aGvBHtL5Kix6lCkv@pollux> (raw)
In-Reply-To: <20250706035944.18442-3-sergeantsagara@protonmail.com>
On Sun, Jul 06, 2025 at 04:00:32AM +0000, Rahul Rameshbabu wrote:
> Device instances in the pci crate represent a valid struct pci_dev, not a
> struct device.
>
> Fixes: 7b948a2af6b5 ("rust: pci: fix unrestricted &mut pci::Device")
> Signed-off-by: Rahul Rameshbabu <sergeantsagara@protonmail.com>
Applied to driver-core-testing, thanks!
prev parent reply other threads:[~2025-07-07 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-06 4:00 [PATCH v2] rust: pci: fix documentation related to Device instances Rahul Rameshbabu
2025-07-07 12:44 ` Danilo Krummrich [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=aGvBHtL5Kix6lCkv@pollux \
--to=dakr@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=bhelgaas@google.com \
--cc=kwilczynski@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sergeantsagara@protonmail.com \
--cc=wt@penguintechs.org \
/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).