From: Fiona Ebner <f.ebner@proxmox.com>
To: Christian Ludwig <christian_ludwig@genua.de>,
pve-devel@lists.proxmox.com
Subject: Re: [PATCH v2 pve-storage 2/16] test: get_subdir: cover the efi-firmware content type
Date: Mon, 5 Oct 2026 16:36:56 +0200 [thread overview]
Message-ID: <c0e74acf-7807-4668-8b66-89610eb0d900@proxmox.com> (raw)
In-Reply-To: <cef728653e9637d84543b79daae31f740816feb0.1790337423.git@genua.de>
Am 28.09.26 um 7:48 AM schrieb Christian Ludwig:
> Check that the vtype maps to the efi-firmware/ subdirectory.
>
> Signed-off-by: Christian Ludwig <christian_ludwig@genua.de>
> ---
> src/test/get_subdir_test.pm | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/src/test/get_subdir_test.pm b/src/test/get_subdir_test.pm
> index 5fb5445..5be6de8 100644
> --- a/src/test/get_subdir_test.pm
> +++ b/src/test/get_subdir_test.pm
> @@ -19,6 +19,8 @@ my $tests = [
> # failed matches
> [$scfg_with_path, 'none', "unknown vtype 'none'\n"],
> [{}, 'iso', "storage definition has no path\n"],
> + # efi-firmware vtype returns <path>/efi-firmware
> + [$scfg_with_path, 'efi-firmware', "$scfg_with_path->{path}/efi-firmware"],
> ];
>
> # creates additional positive tests
It's already covered by the tests here like other content types, but it
also doesn't hurt to have it be explicit, so:
Reviewed-by: Fiona Ebner <f.ebner@proxmox.com>
next prev parent reply other threads:[~2026-10-05 14:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 5:47 [PATCH v2 0/16] Support for custom EFI firmware Christian Ludwig
2026-09-28 5:47 ` [PATCH v2 pve-storage 1/16] plugin: add efi-firmware content type Christian Ludwig
2026-10-05 14:37 ` Fiona Ebner
2026-09-28 5:47 ` [PATCH v2 pve-storage 2/16] test: get_subdir: cover the " Christian Ludwig
2026-10-05 14:36 ` Fiona Ebner [this message]
2026-09-28 5:48 ` [PATCH v2 pve-storage 3/16] plugins: allow the efi-firmware content type on file based storages Christian Ludwig
2026-10-05 14:36 ` Fiona Ebner
2026-09-28 5:48 ` [PATCH v2 pve-storage 4/16] api: status: support efi-firmware in upload and download-url Christian Ludwig
2026-10-05 14:37 ` Fiona Ebner
2026-09-28 5:48 ` [PATCH v2 pve-storage 5/16] test: volume access: cover efi-firmware volumes Christian Ludwig
2026-10-05 14:36 ` Fiona Ebner
2026-09-28 5:48 ` [PATCH v2 pve-storage 6/16] test: list volumes: " Christian Ludwig
2026-10-05 14:37 ` Fiona Ebner
2026-09-28 5:48 ` [PATCH v2 qemu-server 07/16] config: add the efi-firmware option Christian Ludwig
2026-10-05 14:37 ` Fiona Ebner
2026-09-28 5:48 ` [PATCH v2 qemu-server 08/16] api: allow setting " Christian Ludwig
2026-10-05 14:36 ` Fiona Ebner
2026-09-28 5:48 ` [PATCH v2 qemu-server 09/16] ovmf: use a custom firmware image if configured Christian Ludwig
2026-10-05 14:36 ` Fiona Ebner
2026-09-28 5:48 ` [PATCH v2 qemu-server 10/16] test: efi-firmware key in VM config Christian Ludwig
2026-09-28 5:48 ` [PATCH v2 qemu-server 11/16] test: efi-firmware volumes replication Christian Ludwig
2026-09-28 5:48 ` [PATCH v2 pve-manager 12/16] ui: storage: add efi-firmware content type support Christian Ludwig
2026-09-28 5:48 ` [PATCH v2 pve-manager 13/16] ui: form: support other content types in the ISO selector Christian Ludwig
2026-09-28 5:48 ` [PATCH v2 pve-manager 14/16] ui: qemu: allow selecting a custom EFI firmware image Christian Ludwig
2026-09-28 5:48 ` [PATCH v2 pve-docs 15/16] pvesm: document the efi-firmware content type Christian Ludwig
2026-09-28 5:48 ` [PATCH v2 pve-docs 16/16] qm: document the efi-firmware VM option Christian Ludwig
2026-10-05 14:36 ` [PATCH v2 0/16] Support for custom EFI firmware Fiona Ebner
2026-10-08 8:37 ` Christian Ludwig
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=c0e74acf-7807-4668-8b66-89610eb0d900@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=christian_ludwig@genua.de \
--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