From: Dominik Csapak <d.csapak@proxmox.com>
To: Elias Huhsovitz <e.huhsovitz@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH docs 1/4] qm_memory: update dead links in qm_memory_encryption_sev section on AMD SEV
Date: Fri, 10 Jul 2026 09:02:41 +0200 [thread overview]
Message-ID: <a680a33f-8a7c-4875-8164-eddc589eeb87@proxmox.com> (raw)
In-Reply-To: <20260708130453.166084-2-e.huhsovitz@proxmox.com>
it's probably fine here, but we could think about linking to an
archive.org page when the docs pages frequently change their urls...
Aside from that
Reviewed-by: Dominik Csapak <d.csapak@proxmox.com>(
On 7/8/26 3:05 PM, Elias Huhsovitz wrote:
> The section on AMD SEV included dead links.
> Replace dead links with up-to-date working links.
>
> Signed-off-by: Elias Huhsovitz <e.huhsovitz@proxmox.com>
> ---
> qm.adoc | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/qm.adoc b/qm.adoc
> index 96ba68b..8213758 100644
> --- a/qm.adoc
> +++ b/qm.adoc
> @@ -922,10 +922,9 @@ Links:
> * https://developer.amd.com/sev/
> * https://github.com/AMDESE/AMDSEV
> * https://www.qemu.org/docs/master/system/i386/amd-memory-encryption.html
> -* https://www.amd.com/system/files/TechDocs/55766_SEV-KM_API_Specification.pdf
> -* https://documentation.suse.com/sles/15-SP1/html/SLES-amd-sev/index.html
> -* https://www.amd.com/content/dam/amd/en/documents/epyc-technical-docs/specifications/56860.pdf[
> -SEV Secure Nested Paging Firmware ABI Specification]
> +* https://docs.amd.com/v/u/en-US/55766_PUB_3.24_SEV_API
> +* https://documentation.suse.com/sles/15-SP7/single-html/SLES-amd-sev/article-amd-sev.html
> +* https://www.amd.com/content/dam/amd/en/documents/developer/56860.pdf[SEV Secure Nested Paging Firmware ABI Specification]
>
> [[qm_network_device]]
> Network Device
next prev parent reply other threads:[~2026-07-10 7:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 13:04 [PATCH docs/manager 0/4] manager/docs: fix: #6211: ui: docs: add reference to vm options protection/IDX/SEV Elias Huhsovitz
2026-07-08 13:04 ` [PATCH docs 1/4] qm_memory: update dead links in qm_memory_encryption_sev section on AMD SEV Elias Huhsovitz
2026-07-10 7:02 ` Dominik Csapak [this message]
2026-07-08 13:04 ` [PATCH docs 2/4] qm_memory: expand qm_memory_encryption documentation to include Intel TDX Elias Huhsovitz
2026-07-10 7:02 ` Dominik Csapak
2026-07-08 13:04 ` [PATCH manager 3/4] fix #6211: ui: vm: options: Elias Huhsovitz
2026-07-10 7:03 ` Dominik Csapak
2026-07-08 13:04 ` [PATCH manager 4/4] " Elias Huhsovitz
2026-07-10 7:08 ` Dominik Csapak
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=a680a33f-8a7c-4875-8164-eddc589eeb87@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=e.huhsovitz@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