From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fiona Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH qemu] savevm-async: fix function name in error message
Date: Tue, 24 Jan 2023 17:09:11 +0100 [thread overview]
Message-ID: <d439237a-af2b-488d-b0fd-703fa5a12dcf@proxmox.com> (raw)
In-Reply-To: <20230123114323.99098-1-f.ebner@proxmox.com>
Am 23/01/2023 um 12:43 schrieb Fiona Ebner:
> which also makes it distinguishable from the other
> "qemu_savevm_state_iterate error" message.
>
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
> ...17-PVE-add-savevm-async-for-background-state-snapshots.patch | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
applied, thanks!
prev parent reply other threads:[~2023-01-24 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 11:43 [pve-devel] " Fiona Ebner
2023-01-24 16:09 ` 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=d439237a-af2b-488d-b0fd-703fa5a12dcf@proxmox.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal