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 9F6BE1FF140 for ; Fri, 27 Mar 2026 10:41:55 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7DE885A0; Fri, 27 Mar 2026 10:42:17 +0100 (CET) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Fri, 27 Mar 2026 10:41:43 +0100 Message-Id: Subject: Re: [PATCH perl-rs v2 12/40] pve-rs: resource-scheduling: move pve_static into resource_scheduling module From: "Dominik Rusovac" To: "Daniel Kral" , X-Mailer: aerc 0.20.0 References: <20260324183029.1274972-1-d.kral@proxmox.com> <20260324183029.1274972-13-d.kral@proxmox.com> In-Reply-To: <20260324183029.1274972-13-d.kral@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1774604454127 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.299 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 SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: 5LQB5YB4D3NT5FZ6SDHJFDWGODL4PWOH X-Message-ID-Hash: 5LQB5YB4D3NT5FZ6SDHJFDWGODL4PWOH X-MailFrom: d.rusovac@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: lgtm=20 On Tue Mar 24, 2026 at 7:29 PM CET, Daniel Kral wrote: > This is in preparation to add the upcoming pve_dynamic bindings, which > shares much of the same code paths as the pve_static implementation. > > Signed-off-by: Daniel Kral > --- > changes v1 -> v2: > - move it in front of other changes done to pve_static so the code that > is shared with the upcoming pve_dynamic can already be put in separate > modules (as suggested by @Thomas) > - add more context and motivation to patch message [snip] Reviewed-by: Dominik Rusovac