From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Dominik Csapak <d.csapak@proxmox.com>
Subject: partially-applied: [PATCH common/manager/proxmox-perl-rs/qemu-server v2 0/5] use NVML for vGPU info querying
Date: Wed, 13 May 2026 04:54:12 +0200 [thread overview]
Message-ID: <177864064990.4038205.13485271414895283150.b4-ty@b4> (raw)
In-Reply-To: <20260402112212.2294356-1-d.csapak@proxmox.com>
On Thu, 02 Apr 2026 13:21:59 +0200, Dominik Csapak wrote:
> This series replaces Christoph's previous series[0]
>
> It's more or less a rewrite, thus no v2 or similar, but some patches directly
> take code from Christoph's attempt, so i marked those commits as
> co-developed-by.
>
> Changes:
>
> [...]
Applied the perl-rs bindings for now so that the next bump makes them
available, please holler when that happened (or resend the rest), thanks!
[proxmox-perl-rs]:
[1/1] pve: add binding for accessing vgpu info
commit: 278f239a91b14d21c1887e35d48b6ee2f0690f45
next prev parent reply other threads:[~2026-05-13 2:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 11:21 [PATCH common/manager/proxmox-perl-rs/qemu-server v2 0/5] use NVML for vGPU info querying Dominik Csapak
2026-04-02 11:22 ` [PATCH proxmox-perl-rs v2 1/1] pve: add binding for accessing vgpu info Dominik Csapak
2026-04-02 11:22 ` [PATCH qemu-server v2 1/2] pci: move mdev related code to own module Dominik Csapak
2026-04-02 11:22 ` [PATCH qemu-server v2 2/2] pci: mdev: use PVE::RS::NVML for nvidia mdev information Dominik Csapak
2026-04-02 11:22 ` [PATCH manager v2 1/1] api: hardware: pci: use NVML for querying " Dominik Csapak
2026-04-02 11:22 ` [PATCH common v2 1/1] sysfs tools: remove moved code Dominik Csapak
2026-05-12 14:48 ` [PATCH common/manager/proxmox-perl-rs/qemu-server v2 0/5] use NVML for vGPU info querying Dominik Csapak
2026-05-13 2:54 ` Thomas Lamprecht [this message]
2026-05-15 6:15 ` paritally-applied: " Thomas Lamprecht
2026-05-15 10:19 ` applied: " Thomas Lamprecht
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=177864064990.4038205.13485271414895283150.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=pve-devel@lists.proxmox.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