All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cornelia Huck <cohuck@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-dev] [PATCH] editorial: update S390 Common I/O link
Date: Tue, 10 May 2022 09:47:40 -0400	[thread overview]
Message-ID: <20220510094721-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <87wnet1po6.fsf@redhat.com>

On Tue, May 10, 2022 at 03:29:45PM +0200, Cornelia Huck wrote:
> 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>
> > ---
> >  introduction.tex | 3 ++-
> >  1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/introduction.tex b/introduction.tex
> > index 4dc7085..0a78e78 100644
> > --- a/introduction.tex
> > +++ b/introduction.tex
> > @@ -45,7 +45,8 @@ \section{Normative References}\label{sec:Normative References}
> >  IDentifier (UUID) URN Namespace'', RFC 4122, DOI 10.17487/RFC4122,
> >  July 2005. \newline\url{http://www.ietf.org/rfc/rfc4122.txt}\\
> >  	\phantomsection\label{intro:S390 PoP}\textbf{[S390 PoP]} & z/Architecture Principles of Operation, IBM Publication SA22-7832, \newline\url{http://publibfi.boulder.ibm.com/epubs/pdf/dz9zr009.pdf}, and any future revisions\\
> > -	\phantomsection\label{intro:S390 Common I/O}\textbf{[S390 Common I/O]} & ESA/390 Common I/O-Device and Self-Description, IBM Publication SA22-7204, \newline\url{http://publibfp.dhe.ibm.com/cgi-bin/bookmgr/BOOKS/dz9ar501/CCONTENTS}, and any future revisions\\
> > +	\phantomsection\label{intro:S390 Common I/O}\textbf{[S390
> > +Common I/O]} & ESA/390 Common I/O-Device and Self-Description, IBM Publication SA22-7204-01, \newline\url{https://www.ibm.com/resources/publications/OutputPubsDetails?PubID=SA22720401}, and any future revisions\\
> 
> Ok, in the context diff I see that we don't use any suffix for the PoP,
> so I guess that we shouldn't use a suffix here, either.

Sorry I don't really understand what you are saying here.
Is this an ack?

> >  	\phantomsection\label{intro:PCI}\textbf{[PCI]} &
> >  	Conventional PCI Specifications,
> >  	\newline\url{http://www.pcisig.com/specifications/conventional/},


      reply	other threads:[~2022-05-10 13:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 13:10 [virtio-dev] [PATCH] editorial: update S390 Common I/O link Michael S. Tsirkin
2022-05-10 13:29 ` Cornelia Huck
2022-05-10 13:47   ` Michael S. Tsirkin [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=20220510094721-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=cohuck@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.