From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Christoph Heiss <c.heiss@proxmox.com>
Subject: [pve-devel] applied: [PATCH installer v3 00/15] support network interface name pinning
Date: Wed, 12 Nov 2025 08:13:30 +0100 [thread overview]
Message-ID: <176293160701.702025.15190664034961227934.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251111140014.1443471-1-c.heiss@proxmox.com>
On Tue, 11 Nov 2025 14:59:50 +0100, Christoph Heiss wrote:
> This series adds support for pinning the names of network interfaces
> directly during the installation, for all of GUI, TUI and auto-installer.
>
> There are also some smaller clean-ups and quality-of-life improvements
> interspersed - to keep the patches for each part of the installer
> together - in the series, which can also be applied
> separately/beforehand if wanted.
>
> [...]
Applied, with the commit message of the first patch reworked to clarify that
the problem was that the method wasn't exported and adapting patch 14/15 with
s/parentwindow/parent_window/ for legibility (I see no advantage in "gluing"
words together), thanks!
[01/15] test: parse-kernel-cmdline: fix module import statement
commit: af803841c1fc574f5bf941810dfb479addcc9359
[02/15] install: add support for network interface name pinning
commit: dbf15f2efc17ee2b6064c8c374b0bfc75a53f92a
[03/15] run env: network: add kernel driver name to network interface info
commit: 729d3fbb907c50d12bcc880599fef82009a6af10
[04/15] common: utils: fix clippy warnings
commit: 4f0eb2cb7fdaeb7c9956358ba6ddb08c727bb307
[05/15] common: setup: simplify network address list serialization
commit: c4f06bbc5ee8a1c0b90c332fc415a1736d5452db
[06/15] common: implement support for `network_interface_pin_map` config
commit: abe9c548a31b9e2d4c2a33ae7b7d1644815bb5ff
[07/15] auto: add support for pinning network interface names
commit: bb621a816ee7c54d87d539839bc0a6471ab16ac9
[08/15] assistant: verify network settings in `validate-answer` subcommand
commit: b3b59ee6e15c1986f286aeee2bbbe342bd16ef0d
[09/15] post-hook: avoid redundant Option<bool> for (de-)serialization
commit: 0ed4c015592258abeb63c9babbd4bb2488266e08
[10/15] post-hook: add network interface name and pinning status
commit: 9527a9a091a9a2f1606541bc1a325548a3895551
[11/15] tui: views: move network options view to own module
commit: f018da27c1de6bd45ced598a76c5a158d1b0cab7
[12/15] tui: views: form: allow attaching user-defined data to children
commit: 350f13ec8ef6537d836398db3c7cd487c0449293
[13/15] tui: add support for pinning network interface names
commit: 437abf01c8aed0c9a761b1fa6c534ed71d86064f
[14/15] ui: gtk3: allow passing of dialog parent window
commit: f1fde3de46a9a86f2ae63670183cd84f47b46e55
[15/15] gui: add support for pinning network interface names
commit: adb85e8e2a0ff44095cbb7316adadecf9df995e7
_______________________________________________
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-11-12 7:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 13:59 [pve-devel] " Christoph Heiss
2025-11-11 13:59 ` [pve-devel] [PATCH installer v3 01/15] test: parse-kernel-cmdline: fix module import statement Christoph Heiss
2025-11-11 13:59 ` [pve-devel] [PATCH installer v3 02/15] install: add support for network interface name pinning Christoph Heiss
2025-11-11 13:59 ` [pve-devel] [PATCH installer v3 03/15] run env: network: add kernel driver name to network interface info Christoph Heiss
2025-11-11 13:59 ` [pve-devel] [PATCH installer v3 04/15] common: utils: fix clippy warnings Christoph Heiss
2025-11-11 13:59 ` [pve-devel] [PATCH installer v3 05/15] common: setup: simplify network address list serialization Christoph Heiss
2025-11-11 13:59 ` [pve-devel] [PATCH installer v3 06/15] common: implement support for `network_interface_pin_map` config Christoph Heiss
2025-11-11 13:59 ` [pve-devel] [PATCH installer v3 07/15] auto: add support for pinning network interface names Christoph Heiss
2025-11-11 13:59 ` [pve-devel] [PATCH installer v3 08/15] assistant: verify network settings in `validate-answer` subcommand Christoph Heiss
2025-11-11 13:59 ` [pve-devel] [PATCH installer v3 09/15] post-hook: avoid redundant Option<bool> for (de-)serialization Christoph Heiss
2025-11-11 14:00 ` [pve-devel] [PATCH installer v3 10/15] post-hook: add network interface name and pinning status Christoph Heiss
2025-11-11 14:00 ` [pve-devel] [PATCH installer v3 11/15] tui: views: move network options view to own module Christoph Heiss
2025-11-11 14:00 ` [pve-devel] [PATCH installer v3 12/15] tui: views: form: allow attaching user-defined data to children Christoph Heiss
2025-11-11 14:00 ` [pve-devel] [PATCH installer v3 13/15] tui: add support for pinning network interface names Christoph Heiss
2025-11-11 14:00 ` [pve-devel] [PATCH installer v3 14/15] ui: gtk3: allow passing of dialog parent window Christoph Heiss
2025-11-11 14:00 ` [pve-devel] [PATCH installer v3 15/15] gui: add support for pinning network interface names Christoph Heiss
2025-11-11 16:49 ` Stoiko Ivanov
2025-11-11 15:04 ` [pve-devel] [PATCH installer v3 00/15] support network interface name pinning Thomas Lamprecht
2025-11-12 12:00 ` Christoph Heiss
2025-11-11 17:12 ` Stoiko Ivanov
2025-11-12 7:13 ` 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=176293160701.702025.15190664034961227934.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=c.heiss@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 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.