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 CAEF61FF183 for ; Wed, 30 Jul 2025 13:39:50 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 2E5A4B8F2; Wed, 30 Jul 2025 13:41:14 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Filip Schauer Date: Wed, 30 Jul 2025 13:40:15 +0200 Message-ID: <175387561460.3457444.7856999064631567322.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.2 In-Reply-To: <20250728124800.96685-1-f.schauer@proxmox.com> References: <20250728124800.96685-1-f.schauer@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1753875659649 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.031 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-series: [PATCH container v4 0/4] implement device hotplug 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 Mon, 28 Jul 2025 14:47:48 +0200, Filip Schauer wrote: > For now this only includes adding devices to a running container. > (not removing or editing existing devices) > > Changes since v3: > * Rebase onto new master (b3163a6125cb) and adopt new perltidy format > * Validate device with get_device_mode_and_rdev helper > > [...] Applied, thanks! As mentioned in a separate reply, please take a look if re-serializing the pending option is really sensible/useful here. [1/4] extract apparmor profile & namespace switch to a helper commit: 4721f8e653444c9a069b8b235eb512a293a6bc2f [2/4] extract passthrough device node creation to a helper commit: 2ea0dff57306133f33867ed6c7ce1a4b3a14ce4b [3/4] config: support printing a device commit: a568007b2f1f03bd23aec213b1c1578383ef2cf4 [4/4] implement device hotplug commit: c702167e575888072f5cbb34d1a2d1828c26e1f3 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel