Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: Halil Pasic <pasic@linux.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: virtio-comment@lists.oasis-open.org,
	virtio-dev@lists.oasis-open.org, virtio@lists.oasis-open.org,
	Paul Knight <paul.knight@oasis-open.org>,
	Halil Pasic <pasic@linux.ibm.com>
Subject: Re: [virtio-comment] [PATCH] editorial: introduction: fix IBM link
Date: Fri, 15 Jul 2022 18:56:16 +0200	[thread overview]
Message-ID: <20220715185616.58042258.pasic@linux.ibm.com> (raw)
In-Reply-To: <20220713205126.406514-1-mst@redhat.com>

On Wed, 13 Jul 2022 16:51:27 -0400
"Michael S. Tsirkin" <mst@redhat.com> wrote:

> OLD
> 
> [S390    z/Architecture Principles of Operation, IBM Publication SA22-7832,
> PoP]     http://publibfi.boulder.ibm.com/epubs/pdf/dz9zr009.pdf, and any future
>          revisions  
> 
> NEW (should be)
> 
> [S390 PoP] z/Architecture Principles of Operation, IBM Publication SA22-7832,
> https://www.ibm.com/docs/en/SSQ2R2_15.0.0/com.ibm.tpf.toolkit.hlasm.doc/
> dz9zr006.pdf, and any future revisions
> 
> [only changes the hyperlink]
> 
> Reported-by: Paul Knight <paul.knight@oasis-open.org>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

Hm, the new link links to an older revision... The old link seems to
work for me, but I don't know which one is more canonical and supposed
to be more robust. Will do some digging. The new one does look cleaner
though.

Regards,
Halil

This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/


      reply	other threads:[~2022-07-15 16:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13 20:51 [virtio] [PATCH] editorial: introduction: fix IBM link Michael S. Tsirkin
2022-07-15 16:56 ` Halil Pasic [this message]

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=20220715185616.58042258.pasic@linux.ibm.com \
    --to=pasic@linux.ibm.com \
    --cc=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