From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id BD23A1FF15C for ; Fri, 5 Sep 2025 19:42:44 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 66ABC1A58E; Fri, 5 Sep 2025 19:42:54 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Daniel Kral Date: Fri, 5 Sep 2025 19:40:21 +0200 Message-ID: <175709401681.1395682.1807975222670822131.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.2 In-Reply-To: <20250905142249.219371-1-d.kral@proxmox.com> References: <20250905142249.219371-1-d.kral@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1757094122511 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.029 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 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. 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 manager] parser: qemu cpu: also allow kebab-cased properties while parsing 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 Fri, 05 Sep 2025 16:22:21 +0200, Daniel Kral wrote: > There are quite a few kebab-cased properties in the QEMU CPU config, > such as phys-bits and guest-phys-bits. These are currently not exposed > through the web interface, but only the command line. > > If the QEMU CPU config is parsed, it will return undefined with an > error and will break the ProcessorEdit component so that changes cannot > be submitted anymore. > > [...] Applied with squashing in a fixup to make the biome linter happy again, as escaping the - as written was not required, while this is just a warning when installing directly, we turn warnings into errors when building an actual debian package, thanks! [1/1] parser: qemu cpu: also allow kebab-cased properties while parsing commit: 2ddc4d864b59ed93b43b7bf2581b3eac32e8bfac _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel