On Thu, May 30, 2019 at 16:06:54 +0200, Erik Skultety wrote: > The SEV whitepaper link stopped working as the resource has been moved. > But all the SEV-related stuff like spec, whitepaper, presentations, etc. > are being provided at https://developer.amd.com/sev/ which may look like > a more stable resource (in terms of not being removed in the foreseeable > future) so rather than providing and maintaining links to individual > resources, let's use this one instead. > > Signed-off-by: Erik Skultety <eskultet@xxxxxxxxxx> > --- > docs/formatdomaincaps.html.in | 5 +---- > 1 file changed, 1 insertion(+), 4 deletions(-) > > diff --git a/docs/formatdomaincaps.html.in b/docs/formatdomaincaps.html.in > index 432d7aed5e..ef42bd57c3 100644 > --- a/docs/formatdomaincaps.html.in > +++ b/docs/formatdomaincaps.html.in > @@ -518,10 +518,7 @@ > a look at the following resources: > <dl> > <dd> > - <a href="https://support.amd.com/TechDocs/55766_SEV-KM_API_Specification.pdf";>SEV API spec</a> > - </dd> > - <dd> > - <a href="http://amd-dev.wpengine.netdna-cdn.com/wordpress/media/2013/12/AMD_Memory_Encryption_Whitepaper_v7-Public.pdf";>SEV White Paper</a> > + <a href="https://developer.amd.com/sev/";>SEV further reading</a> I think that at this point we should no longer link to AMDs page if they are unable to provide a functioning persistent link.
Attachment:
signature.asc
Description: PGP signature
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
