From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Fiona Ebner <f.ebner@proxmox.com>
Subject: applied: [PATCH-SERIES qemu-server 0/4] adapt to deprecated and removed features for QEMU 11
Date: Mon, 18 May 2026 12:46:24 +0200 [thread overview]
Message-ID: <177909704336.3037978.8948433096156605654.b4-ty@b4> (raw)
In-Reply-To: <20260512120959.169149-1-f.ebner@proxmox.com>
On Tue, 12 May 2026 14:09:47 +0200, Fiona Ebner wrote:
> Just two small things:
> 1. The 'debug-threads' option for enabling thread names for debugging
> is now enabled by default and the option is deprecated.
> 2. Some rather niche HMP commands are deprecated.
>
> qemu-server:
>
> [...]
Applied, thanks!
[1/4] cfg2cmd: avoid using deprecated 'debug-threads' option with QEMU binary >= 11.0
commit: 0bde956c51fd81a004bb009dae7ad5aa2e6d264d
[2/4] api: hmp permissions: use v5.36 for module
commit: af61d4dcbc74851794b2dc9b47bedb2ed023293a
[3/4] api: hmp permissions: make return explicit
commit: 950eb3d37b907a54043dcb77ff071b4760c0a277
[4/4] api: human monitor: warn about deprecated commands
commit: 47300494940f11baa392a0640a2966216243b904
Tiny drive-by on top of 4/4: `make tidy` flagged the new warn line as too
long, applied the wrap as a separate commit (a617e3010).
prev parent reply other threads:[~2026-05-18 10:46 UTC|newest]
Thread overview: 6+ 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 ` [PATCH qemu-server 2/4] api: hmp permissions: use v5.36 for module Fiona Ebner
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
2026-05-18 10:46 ` Thomas Lamprecht [this message]
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=177909704336.3037978.8948433096156605654.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=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