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] add QAPI naming exceptions in patches introducing them
Date: Wed, 11 Jan 2023 10:15:32 +0100 [thread overview]
Message-ID: <149d9f75-0611-a198-6047-990ac038ec80@proxmox.com> (raw)
In-Reply-To: <20230110084057.61968-1-f.ebner@proxmox.com>
Am 10/01/2023 um 09:40 schrieb Fiona Ebner:
> Avoids a patch and is required to compile when not all patches are
> applied. No functional change is intended.
>
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
> .../0007-PVE-Up-qmp-add-get_link_status.patch | 18 +++++++---
> ...virtio-balloon-improve-query-balloon.patch | 17 +++++++++-
> ...k-driver-to-map-backup-archives-into.patch | 15 ++++++++-
> ...register-yank-before-migration_inco.patch} | 0
> ...valid-QAPI-names-for-backwards-compa.patch | 33 -------------------
> ...add-l-option-for-loading-a-snapshot.patch} | 0
> ...h => 0051-vma-allow-partial-restore.patch} | 0
> ...patch => 0052-pbs-namespace-support.patch} | 0
> ...rbd-workaround-for-ceph-issue-53784.patch} | 0
> ...fix-handling-of-holes-in-.bdrv_co_b.patch} | 0
> ...-rbd-implement-bdrv_co_block_status.patch} | 0
> ...-jobs-correctly-cancel-in-error-sce.patch} | 0
> ...sure-jobs-in-di_list-are-referenced.patch} | 0
> ...-segfault-issues-upon-backup-cancel.patch} | 0
> ...upport-64KiB-unaligned-input-images.patch} | 0
> ...-triggering-assertion-in-error-case.patch} | 0
> ...k-alloc-track-avoid-premature-break.patch} | 0
> ...passing-max-workers-performance-set.patch} | 0
> debian/patches/series | 29 ++++++++--------
> 19 files changed, 58 insertions(+), 54 deletions(-)
> rename debian/patches/pve/{0050-PVE-savevm-async-register-yank-before-migration_inco.patch => 0049-PVE-savevm-async-register-yank-before-migration_inco.patch} (100%)
> delete mode 100644 debian/patches/pve/0049-PVE-whitelist-invalid-QAPI-names-for-backwards-compa.patch
> rename debian/patches/pve/{0051-qemu-img-dd-add-l-option-for-loading-a-snapshot.patch => 0050-qemu-img-dd-add-l-option-for-loading-a-snapshot.patch} (100%)
> rename debian/patches/pve/{0052-vma-allow-partial-restore.patch => 0051-vma-allow-partial-restore.patch} (100%)
> rename debian/patches/pve/{0053-pbs-namespace-support.patch => 0052-pbs-namespace-support.patch} (100%)
> rename debian/patches/pve/{0054-Revert-block-rbd-workaround-for-ceph-issue-53784.patch => 0053-Revert-block-rbd-workaround-for-ceph-issue-53784.patch} (100%)
> rename debian/patches/pve/{0055-Revert-block-rbd-fix-handling-of-holes-in-.bdrv_co_b.patch => 0054-Revert-block-rbd-fix-handling-of-holes-in-.bdrv_co_b.patch} (100%)
> rename debian/patches/pve/{0056-Revert-block-rbd-implement-bdrv_co_block_status.patch => 0055-Revert-block-rbd-implement-bdrv_co_block_status.patch} (100%)
> rename debian/patches/pve/{0057-PVE-Backup-create-jobs-correctly-cancel-in-error-sce.patch => 0056-PVE-Backup-create-jobs-correctly-cancel-in-error-sce.patch} (100%)
> rename debian/patches/pve/{0058-PVE-Backup-ensure-jobs-in-di_list-are-referenced.patch => 0057-PVE-Backup-ensure-jobs-in-di_list-are-referenced.patch} (100%)
> rename debian/patches/pve/{0059-PVE-Backup-avoid-segfault-issues-upon-backup-cancel.patch => 0058-PVE-Backup-avoid-segfault-issues-upon-backup-cancel.patch} (100%)
> rename debian/patches/pve/{0060-vma-create-support-64KiB-unaligned-input-images.patch => 0059-vma-create-support-64KiB-unaligned-input-images.patch} (100%)
> rename debian/patches/pve/{0061-vma-create-avoid-triggering-assertion-in-error-case.patch => 0060-vma-create-avoid-triggering-assertion-in-error-case.patch} (100%)
> rename debian/patches/pve/{0062-block-alloc-track-avoid-premature-break.patch => 0061-block-alloc-track-avoid-premature-break.patch} (100%)
> rename debian/patches/pve/{0063-PVE-Backup-allow-passing-max-workers-performance-set.patch => 0062-PVE-Backup-allow-passing-max-workers-performance-set.patch} (100%)
>
>
applied, thanks!
prev parent reply other threads:[~2023-01-11 9:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 8:40 [pve-devel] " Fiona Ebner
2023-01-11 9:15 ` 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=149d9f75-0611-a198-6047-990ac038ec80@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox