From: Halil Pasic <pasic@linux.ibm.com>
To: virtio@lists.oasis-open.org, virtio-dev@lists.oasis-open.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
Pawel Moll <pawel.moll@arm.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Halil Pasic <pasic@linux.ibm.com>
Subject: [virtio] [PATCH v3 0/6] rework notifications terminology
Date: Mon, 25 Jun 2018 14:21:26 +0200 [thread overview]
Message-ID: <1529929292-11900-1-git-send-email-pasic@linux.ibm.com> (raw)
Abstract
--------
The terminology around notifications is currently somewhat
fragmented. Unify notifications terminology using available and used
buffer notification consistently for the virtqueue notifications.
Consistent use of the term configuration change notification is of
concern.
Changelog:
---------
v2 -> v3:
* Addressed all comments from the previous round
* Added r-b's
v1 -> v2:
* Addressed Stefan's comments (mostly typos, grammar and inconsistencies).
Thanks Stefan!
* Rebased onto the current master.
RFC -> v1:
* Devices and the transports PCI and MMIO were omitted.
Now the rework should be complete.
* Addressed review comments and minor changes for the first
three patches.
Halil Pasic (6):
notifications: unify notifications wording in core
notifications: notifications as basic virtio facility
ccw: map common notifications terminology to ccw
pci: map common notifications terminology to PCI
mmio: map common notifications terminology to MMIO
notifications: update notifications terminology for devices
cl-os.tex | 2 +-
conformance.tex | 10 ++--
content.tex | 164 +++++++++++++++++++++++++++++++++++++++++-------------
packed-ring.tex | 60 +++++++++++---------
split-ring.tex | 72 ++++++++++++++----------
5 files changed, 206 insertions(+), 102 deletions(-)
---------------------------------------------------------------------
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 reply other threads:[~2018-06-25 12:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 12:21 Halil Pasic [this message]
2018-06-25 12:21 ` [virtio] [PATCH v3 1/6] notifications: unify notifications wording in core Halil Pasic
2018-06-25 14:45 ` [virtio] " Cornelia Huck
2018-06-25 15:15 ` [virtio] Re: [virtio-dev] " Halil Pasic
2018-06-25 12:21 ` [virtio] [PATCH v3 2/6] notifications: notifications as basic virtio facility Halil Pasic
2018-06-25 14:37 ` [virtio] " Cornelia Huck
2018-06-25 12:21 ` [virtio] [PATCH v3 3/6] ccw: map common notifications terminology to ccw Halil Pasic
2018-06-25 12:21 ` [virtio] [PATCH v3 4/6] pci: map common notifications terminology to PCI Halil Pasic
2018-06-25 12:21 ` [virtio] [PATCH v3 5/6] mmio: map common notifications terminology to MMIO Halil Pasic
2018-06-25 14:34 ` [virtio] " Cornelia Huck
2018-06-25 12:21 ` [virtio] [PATCH v3 6/6] notifications: update notifications terminology for devices Halil Pasic
2018-07-02 15:51 ` [virtio] Re: [PATCH v3 0/6] rework notifications terminology Stefan Hajnoczi
2018-07-03 0:01 ` [virtio] Re: [virtio-dev] " Michael S. Tsirkin
2018-07-03 7:45 ` Cornelia Huck
2018-07-03 9:00 ` Halil Pasic
2018-07-03 12:07 ` [virtio] Re: [virtio-dev] " Halil Pasic
2018-07-17 16:47 ` Halil Pasic
2018-07-27 11:33 ` Halil Pasic
2018-07-27 11:45 ` Michael S. Tsirkin
2018-08-01 13:04 ` Halil Pasic
2018-08-01 22:30 ` Michael S. Tsirkin
2018-08-02 17:12 ` 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=1529929292-11900-1-git-send-email-pasic@linux.ibm.com \
--to=pasic@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=pawel.moll@arm.com \
--cc=stefanha@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 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.