public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH qemu-server 2/4] api: hmp permissions: use v5.36 for module
Date: Tue, 12 May 2026 14:09:49 +0200	[thread overview]
Message-ID: <20260512120959.169149-3-f.ebner@proxmox.com> (raw)
In-Reply-To: <20260512120959.169149-1-f.ebner@proxmox.com>

Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---
 src/PVE/API2/Qemu/HMPPerms.pm | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/src/PVE/API2/Qemu/HMPPerms.pm b/src/PVE/API2/Qemu/HMPPerms.pm
index cadafa9e..deb0a439 100644
--- a/src/PVE/API2/Qemu/HMPPerms.pm
+++ b/src/PVE/API2/Qemu/HMPPerms.pm
@@ -1,7 +1,6 @@
 package PVE::API2::Qemu::HMPPerms;
 
-use strict;
-use warnings;
+use v5.36;
 
 # List of monitor commands and associated required permission. Listed explicitly to be future-proof.
 #
@@ -182,7 +181,7 @@ our $hmp_command_perms = {
     xp => 'Sys.Modify', # physical memory dump starting at 'addr'
 };
 
-sub generate_description {
+sub generate_description() {
     my $cmd_by_priv = {};
     for my $cmd (sort keys $hmp_command_perms->%*) {
         my $priv = $hmp_command_perms->{$cmd};
-- 
2.47.3





  parent reply	other threads:[~2026-05-12 12:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12 12:09 [PATCH-SERIES qemu-server 0/4] adapt to deprecated and removed features for QEMU 11 Fiona Ebner
2026-05-12 12:09 ` [PATCH qemu-server 1/4] cfg2cmd: avoid using deprecated 'debug-threads' option with QEMU binary >= 11.0 Fiona Ebner
2026-05-12 12:09 ` Fiona Ebner [this message]
2026-05-12 12:09 ` [PATCH qemu-server 3/4] api: hmp permissions: make return explicit Fiona Ebner
2026-05-12 12:09 ` [PATCH qemu-server 4/4] api: human monitor: warn about deprecated commands Fiona Ebner

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=20260512120959.169149-3-f.ebner@proxmox.com \
    --to=f.ebner@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal