From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id DAD111FF17E for ; Thu, 13 Nov 2025 21:00:27 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 1E6742724D; Thu, 13 Nov 2025 21:01:21 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Christoph Heiss Date: Thu, 13 Nov 2025 21:00:40 +0100 Message-ID: <176306403669.2651046.8451157541738097242.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20251113135023.1038305-1-c.heiss@proxmox.com> References: <20251113135023.1038305-1-c.heiss@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1763064022697 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.149 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_LOTSOFHASH 0.25 Emails with lots of hash-like gibberish SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] applied: [PATCH installer 0/6] interface name pinning followups X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" On Thu, 13 Nov 2025 14:49:48 +0100, Christoph Heiss wrote: > Some small followups for the initial name pinning support [0]. > > First and foremost makes the interface name checks a bit stricter, to > comply with our `pve-iface` schema - as reported by Stoiko [1]. Thanks! > > Patch #4 & #5 exclude non-physical interfaces from being shown in the > pinning dialog in the GUI and TUI, respectively. While this does change > anything for normal bare-metal installation, it is a) a bit of > future-proofing and b) improves developer/testing experience a bit, as > these interfaces should never be available for pinning anyway. > > [...] Applied, thanks! [1/6] sys: net: pinning: make interface name checks stricter commit: 2033a3576fae1f684024710541508f16b04d72de [2/6] common: pinning: make interface name checks stricter commit: aa0ddcdbff34f8bd3d16e017df3ef160e2e1cdd5 [3/6] test: validate-link-pin-map: give all tests a name commit: 24f69569adcec258edc74190b111e71858e3ca4d [4/6] gui: network: only display pinnable devices in pinning options dialog commit: 3520f0dc1941e06dd4b1192007a3e0e97c7c8f0e [5/6] tui: network: only display pinnable devices in pinning options dialog commit: 32b2ea3bb230c22008f7f3af6c9ab7c433069561 [6/6] tree-wide: run cargo fmt commit: d505f71b3c5da129880ca9b15e95e0946d9933cb _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel