From: "Michael S. Tsirkin" <mst@redhat.com>
To: Halil Pasic <pasic@linux.ibm.com>
Cc: Halil Pasic <pasic@linux.vnet.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
virtio@lists.oasis-open.org, virtio-dev@lists.oasis-open.org,
Cornelia Huck <cohuck@redhat.com>
Subject: Re: [virtio] [PATCH 4/5] packed-ring: reposition drivernormative on driver notifications
Date: Fri, 20 Apr 2018 19:28:58 +0300 [thread overview]
Message-ID: <20180420192339-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <b3946831-bdb2-b1c4-5c47-b917363b0893@linux.ibm.com>
On Fri, Apr 20, 2018 at 06:22:40PM +0200, Halil Pasic wrote:
> Was, kind of, the point I tried to make. I've (for myself) given up on
> these ideals. That's why I did not bother to think about isn't that sentence
> normative section material. And I don't intend to clean up normative
> vs non-normative.
Makes sense.
We do need to keep RFC2119 keywords out of the rest of the text simply to
avoid confusing people - from experience if we don't then during public
review people jump on it immediately and say hey this must go into the
normative section. It's just something that's easy to spot :)
--
MST
---------------------------------------------------------------------
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
next prev parent reply other threads:[~2018-04-20 16:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 18:58 [virtio] [PATCH 0/5] fixes and tweaks for virtio v1.1 Halil Pasic
2018-04-09 18:58 ` [virtio] [PATCH 1/5] packed-ring: fix used descriptors but meant buffers Halil Pasic
2018-04-09 18:58 ` [virtio] [PATCH 2/5] consistency: clean up stale wording for v1.1 terms Halil Pasic
2018-04-10 9:30 ` [virtio] " Cornelia Huck
2018-04-10 10:04 ` Halil Pasic
2018-04-10 10:06 ` Cornelia Huck
2018-04-09 18:58 ` [virtio] [PATCH 3/5] packed-packed: fix supplying buffers description Halil Pasic
2018-04-09 18:58 ` [virtio] [PATCH 4/5] packed-ring: reposition drivernormative on driver notifications Halil Pasic
2018-04-09 19:51 ` Paolo Bonzini
2018-04-10 10:25 ` Halil Pasic
2018-04-10 11:05 ` Paolo Bonzini
2018-04-10 14:59 ` Halil Pasic
2018-04-20 15:45 ` Paolo Bonzini
2018-04-20 15:59 ` Michael S. Tsirkin
2018-04-20 16:22 ` Halil Pasic
2018-04-20 16:28 ` Michael S. Tsirkin [this message]
2018-04-09 18:58 ` [virtio] [PATCH 5/5] packed-ring: tweak driver code example Halil Pasic
2018-04-20 15:00 ` [virtio] [PATCH 0/5] fixes and tweaks for virtio v1.1 Halil Pasic
2018-04-27 16:07 ` 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=20180420192339-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--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