From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Stefan Hanreich <s.hanreich@proxmox.com>
Subject: [pve-devel] applied: [PATCH manager 0/2] add virtual function support to network-interface-pinning
Date: Wed, 23 Jul 2025 19:31:30 +0200 [thread overview]
Message-ID: <175329187878.3836001.9457308287188706867.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250722145223.351778-1-s.hanreich@proxmox.com>
On Tue, 22 Jul 2025 16:52:21 +0200, Stefan Hanreich wrote:
> Instead of generating a .link file for every virtual function, with this patch
> series proxmox-network-interface-pinning now includes a udev rule that
> dynamically changes the name of virtual functions according to the pinned name
> of its parent device.
>
> pve-manager:
>
> [...]
Applied, thanks!
[1/2] configs: add udev helper for pinning virtual function names
commit: 017359f376a78fc2754482207cfdf07a5fd58248
[2/2] network-interface-pinning: do not generate link files for vfs
commit: 73ae711ff01a3934ac745fdef61b0c3b9f28ac03
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-07-23 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 14:52 [pve-devel] " Stefan Hanreich
2025-07-22 14:52 ` [pve-devel] [PATCH pve-manager 1/2] configs: add udev helper for pinning virtual function names Stefan Hanreich
2025-07-22 14:52 ` [pve-devel] [PATCH pve-manager 2/2] network-interface-pinning: do not generate link files for vfs Stefan Hanreich
2025-07-23 17:31 ` Thomas Lamprecht [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=175329187878.3836001.9457308287188706867.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.hanreich@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.