public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: "Gary Guo" <gary@garyguo.net>
To: "Zijing Zhang" <zijing.zhang@ry.rs>, <dakr@kernel.org>,
	<linux-pci@vger.kernel.org>, <rust-for-linux@vger.kernel.org>
Cc: <acourbot@nvidia.com>
Subject: Re: [PATCH] rust: pci: export ConfigSpace
Date: Sat, 31 Jan 2026 16:16:43 +0000	[thread overview]
Message-ID: <DG2WR3EOBWCY.DU3K4LRV4FUE@garyguo.net> (raw)
In-Reply-To: <20260131040232.1243049-1-zijing.zhang@ry.rs>

On Sat Jan 31, 2026 at 4:02 AM GMT, Zijing Zhang wrote:
> Re-export ConfigSpace from kernel::pci so users can name the returned
> type from Device::config_space*().
>
> Fixes: 4dc0bacb1d3c ("rust: pci: add config space read/write support")
> Reviewed-by: Alexandre Courbot <acourbot@nvidia.com>
> Signed-off-by: Zijing Zhang <zijing.zhang@ry.rs>

Please reference the initial bug report in tags:

Reported-by: Gary Guo <gary@garyguo.net>
Closes: https://lore.kernel.org/rust-for-linux/DG2D5ONS18FE.TC7K3O8V8SU1@garyguo.net/

Best,
Gary

> ---
>  rust/kernel/pci.rs | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/rust/kernel/pci.rs b/rust/kernel/pci.rs
> index f347c2f7c3a6..af74ddff6114 100644
> --- a/rust/kernel/pci.rs
> +++ b/rust/kernel/pci.rs
> @@ -42,6 +42,7 @@
>  };
>  pub use self::io::{
>      Bar,
> +    ConfigSpace,
>      ConfigSpaceKind,
>      ConfigSpaceSize,
>      Extended,


  parent reply	other threads:[~2026-01-31 16:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-31  4:02 [PATCH] rust: pci: export ConfigSpace Zijing Zhang
2026-01-31  4:57 ` Alexandre Courbot
2026-01-31 16:16 ` Gary Guo [this message]
2026-01-31 16:42   ` [PATCH v2] " Zijing Zhang
2026-01-31 18:12     ` Miguel Ojeda
2026-02-01 21:33     ` Danilo Krummrich
  -- strict thread matches above, loose matches on Subject: below --
2026-01-31  2:20 [PATCH] " Zijing Zhang
2026-01-31  3:49 ` Alexandre Courbot

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=DG2WR3EOBWCY.DU3K4LRV4FUE@garyguo.net \
    --to=gary@garyguo.net \
    --cc=acourbot@nvidia.com \
    --cc=dakr@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=zijing.zhang@ry.rs \
    /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