Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
	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>,
	Halil Pasic <pasic@linux.ibm.com>
Subject: [virtio] Re: [PATCH v2] editorial: update S390 Common I/O link
Date: Tue, 10 May 2022 16:08:35 +0200	[thread overview]
Message-ID: <87r1511nvg.fsf@redhat.com> (raw)
In-Reply-To: <20220510140130.99846-1-mst@redhat.com>

On Tue, May 10 2022, "Michael S. Tsirkin" <mst@redhat.com> wrote:

> Paul Knight wrote:
>
> In running a link check, I noted several issues, none significant for this
> initial public review publication:
> - broken link in Normative references:
> -- [S390 Common I/O] ESA/390 Common I/O-Device and Self-Description, IBM
> Publication SA22-7204,
> http://publibfp.dhe.ibm.com/cgi-bin/bookmgr/BOOKS/dz9ar501/CCONTENTS, and any
> future revisions
> (This link is currently broken, and I could not find any alternative source for
> this document. - please rewrite the reference to indicate document is no longer
> available at this link. You may also consider whether the solitary citation at
> 4.3.1.3 is still needed.)
> This broken link is not a blocking issue for a Committee specification Draft,
> but it will not be allowed for a Committee Specification.
>
> Reported-by: Paul Knight <paul.knight@oasis-open.org>
> Suggested-by: Halil Pasic <pasic@linux.ibm.com>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
>
> changes from v1:
> 	do not tweak description just the url
>
>  introduction.tex | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)

Reviewed-by: Cornelia Huck <cohuck@redhat.com>


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that 
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 


  reply	other threads:[~2022-05-10 14:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 14:01 [PATCH v2] editorial: update S390 Common I/O link Michael S. Tsirkin
2022-05-10 14:08 ` Cornelia Huck [this message]
2022-05-10 15:57 ` [virtio-dev] " Halil Pasic

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=87r1511nvg.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=mst@redhat.com \
    --cc=pasic@linux.ibm.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