Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Patrick Durusau <patrick@durusau.net>
Cc: virtio-comment@lists.oasis-open.org,
	OASIS TAB <tab@lists.oasis-open.org>
Subject: Re: [virtio-comment] TAB comments on Virtual I/O Device (VIRTIO) Version 1.1
Date: Wed, 27 Feb 2019 10:50:34 -0500	[thread overview]
Message-ID: <20190226194416-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <9bdf3096-734f-a921-d570-f8dfb9300868@durusau.net>

Thanks for the comments!
I would appreciate an advice on the following:

On Thu, Feb 21, 2019 at 05:36:51PM -0500, Patrick Durusau wrote:
> TAB-1668,47707,Virtual I/O Device (VIRTIO) Version 1.1,Bug,"The accessibility site that I commonly use, [https://achecker.ca/checker/index.php,] is down tonight but use it to check your usage for other problems. 

When I attempt to upload the spec to this tool, I receive
a response that the document is too large.
Is there an offline version we could use?

-- 
MST

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/


  parent reply	other threads:[~2019-02-27 15:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-21 22:36 [virtio-comment] TAB comments on Virtual I/O Device (VIRTIO) Version 1.1 Patrick Durusau
2019-02-26 20:58 ` Michael S. Tsirkin
2019-02-26 21:29   ` [virtio-comment] Re: [tab] " Chet Ensign
2019-02-27 14:10     ` Michael S. Tsirkin
2019-02-27 14:20       ` Chet Ensign
2019-02-27 14:31         ` Patrick Durusau
2019-02-27 14:35           ` Chet Ensign
2019-02-27 15:14             ` Michael S. Tsirkin
2019-02-27 15:42               ` Chet Ensign
2019-02-27 15:46                 ` Michael S. Tsirkin
2019-02-27 15:50 ` Michael S. Tsirkin [this message]
2019-02-27 20:49   ` Patrick Durusau

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=20190226194416-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=patrick@durusau.net \
    --cc=tab@lists.oasis-open.org \
    --cc=virtio-comment@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