From: Parav Pandit <parav@nvidia.com>
To: "virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
"mst@redhat.com" <mst@redhat.com>,
"cohuck@redhat.com" <cohuck@redhat.com>,
"david.edmondson@oracle.com" <david.edmondson@oracle.com>
Cc: "virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"sburla@marvell.com" <sburla@marvell.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
Yishai Hadas <yishaih@nvidia.com>,
Maor Gottlieb <maorg@nvidia.com>,
Shahaf Shuler <shahafs@nvidia.com>
Subject: [virtio-comment] RE: [PATCH v15] admin: Add group member legacy register access commands
Date: Thu, 13 Jul 2023 13:44:01 +0000 [thread overview]
Message-ID: <PH0PR12MB548114295F2A6A5747B8B626DC37A@PH0PR12MB5481.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230711150135.222793-1-parav@nvidia.com>
Hi Michael, Cornelia,
> From: Parav Pandit <parav@nvidia.com>
> Sent: Tuesday, July 11, 2023 11:02 AM
> To: virtio-comment@lists.oasis-open.org; mst@redhat.com;
> cohuck@redhat.com; david.edmondson@oracle.com
[..]
> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/167
> Signed-off-by: Parav Pandit <parav@nvidia.com>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
> changelog:
> v14->v15:
> - addressed below editorial comments from Michael
> - replaced 'is' with 'are' for command description
> - simplified wording around ignore and skip to just use ignore
> - to -> in preference to
> - small rewording for flags description
> v13->v14:
> - addressed below comments from Michael
> - reworded BAR 1 to 5 text as_is suggested by Michael
> - added text for skipping invalid entries
> - replaced 'contains' with 'contain'
> - removed 'related to the base address associated'
> - addressed comments from Cornelia
> - added article the at many places
> - replaced does not to do not
> - reworded the driver normative for flags parsing
> v12->v13:
> - added article
> - add hyphen between little and endian
> - mentioned vq index depth of 16-bit
> - rewrote alternative approach line
> - mention vq index, length and endianness in mmio description
> - fixed padding bytes size from 7 to 6 bytes
> - rewrote bar field description
> - offset alignment text added
> - added text to ignore reserved notification entries
> - device and driver conformance lines added for notification info command
> fields
> - dropped group member prefix to the driver
> - reworded text for flags requirements
> - reworded to say all driver notifications in conformance
> - itemize conformance section under command to ease reading
> v11->v12:
> - added missing article the at few places
> - rewrote group_member_id statements like other existing
> commands which is cleaner and shorter
> - added length and alignment lines to multiple commands
> - rewrote fast path to separate dedicated mechanism
> - rewrote example and description para for legacy notification command
> - made separate paragraph for the notify info command
> - dropped citation to virtio pci capabilities for member device
> - notification region changed to notification address throughout
> - added description to all the fields of the info struct
> - avoided union in spirit of keeping all for pci
> - used single listing
> - moved description to end which was in between two structs
> - added 4 entry and preference description
> - added conformance line for notification via mmio works same way as
> admin command
> v10->v11:
> - replaced tab with white spaces in read structure
> - included pci fields along side other generic fields to avoid
> indirection
> - merged pci conformance section
> - avoid using definite in starting introduction
> - replace 'all of the' with 'any of the'
> - changed drivers notification normative to indicate use of
> NOTIFY_INFO command
> - renamed NOTIFY_QUERY to NOTIFY_INFO name
> - merged 4th patch with 3rd
> - added normative line for notify_info command
> - reworded notification region command description to be more verbose
> - merged flags and owner field to indicate end of list
Now that last few iterations handled all the suggested edits,
Can you please start the voting for it?
https://github.com/oasis-tcs/virtio-spec/issues/167
prev parent reply other threads:[~2023-07-13 13:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 15:01 [virtio-comment] [PATCH v15] admin: Add group member legacy register access commands Parav Pandit
2023-07-13 13:44 ` Parav Pandit [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=PH0PR12MB548114295F2A6A5747B8B626DC37A@PH0PR12MB5481.namprd12.prod.outlook.com \
--to=parav@nvidia.com \
--cc=cohuck@redhat.com \
--cc=david.edmondson@oracle.com \
--cc=jasowang@redhat.com \
--cc=maorg@nvidia.com \
--cc=mst@redhat.com \
--cc=sburla@marvell.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=yishaih@nvidia.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).