Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: virtio-comment@lists.oasis-open.org, virtio-dev@lists.oasis-open.org
Cc: virtio@lists.oasis-open.org, Paul Knight <paul.knight@oasis-open.org>
Subject: [virtio-dev] [PATCH] changelog editorial fixes
Date: Tue, 10 May 2022 01:29:31 -0400	[thread overview]
Message-ID: <20220510052929.69133-1-mst@redhat.com> (raw)

Paul Knight reports:

Minor broken links in the "Revision History" - Appendix D
- https://lists.oasis-open.org/archives/virtio-dev/201910/msg00057.html. (bad
link due to inclusion of the terminating period - second item dated 01 Sep 2020
in Appendix D Revision history) - not a blocking issue
-  https://lkml.org/lkml/2020/4/21/1020) (bad link due to including the final
right parenthesis in the hyperlink - item dated 01 Sep 2020 by Petre Eftime) -
not a blocking issue
- https://github.org/oasis-tcs/virtio-spec/issues/97  (bad link due to using
github.org instead of github.com - first item dated 30 Mar 2021 in Appendix D
Revision history) - not a blocking issue

Reported-by: Paul Knight <paul.knight@oasis-open.org>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
 cl-os.tex | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/cl-os.tex b/cl-os.tex
index fa980b2..5ae8a7b 100644
--- a/cl-os.tex
+++ b/cl-os.tex
@@ -688,7 +688,7 @@
 adding it as normative requirement. Existing drivers already depend on
 this.
 
-See also \url{https://lists.oasis-open.org/archives/virtio-dev/201910/msg00057.html.}
+See also \url{https://lists.oasis-open.org/archives/virtio-dev/201910/msg00057.html}.
 
 Fixes: \url{https://github.com/oasis-tcs/virtio-spec/issues/56}
 
@@ -807,7 +807,7 @@
 
 The NitroSecureModule is a device with a very stripped down
 Trusted Platform Module functionality, which is used in the
-context of a Nitro Enclave (see \url{https://lkml.org/lkml/2020/4/21/1020)}
+context of a Nitro Enclave (see \url{https://lkml.org/lkml/2020/4/21/1020})
 to provide boot time measurement and attestation.
 
 Since this device provides some critical cryptographic operations,
@@ -1326,7 +1326,7 @@
 
 Signed-off-by: Enrico Granata <egranata@google.com>
 
-Fixes: \url{https://github.org/oasis-tcs/virtio-spec/issues/97}
+Fixes: \url{https://github.com/oasis-tcs/virtio-spec/issues/97}
 
 Signed-off-by: Cornelia Huck <cohuck@redhat.com>
 
-- 
MST


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


             reply	other threads:[~2022-05-10  5:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10  5:29 Michael S. Tsirkin [this message]
2022-05-10  8:17 ` [virtio-comment] Re: [virtio-dev] [PATCH] changelog editorial fixes Cornelia Huck

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=20220510052929.69133-1-mst@redhat.com \
    --to=mst@redhat.com \
    --cc=paul.knight@oasis-open.org \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=virtio@lists.oasis-open.org \
    /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