From: Parav Pandit <parav@nvidia.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
"cohuck@redhat.com" <cohuck@redhat.com>,
"david.edmondson@oracle.com" <david.edmondson@oracle.com>,
"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 v12 3/3] admin: Add group member legacy register access commands
Date: Fri, 7 Jul 2023 15:32:04 +0000 [thread overview]
Message-ID: <PH0PR12MB5481EDC9C3F7D397FCF34AC4DC2DA@PH0PR12MB5481.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230707043229-mutt-send-email-mst@kernel.org>
> From: Michael S. Tsirkin <mst@redhat.com>
> Sent: Friday, July 7, 2023 5:31 AM
> ok getting there. mostly notification needs a bit more work but it's close.
Fixed all the comments in v13.
Thanks.
next prev parent reply other threads:[~2023-07-07 15:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 3:53 [virtio-comment] [PATCH v12 0/3] admin: Access legacy registers using admin commands Parav Pandit
2023-07-07 3:53 ` [virtio-comment] [PATCH v12 1/3] admin: Split opcode table rows with a line Parav Pandit
2023-07-07 3:54 ` [virtio-comment] [PATCH v12 2/3] admin: Fix section numbering Parav Pandit
2023-07-07 3:54 ` [virtio-comment] [PATCH v12 3/3] admin: Add group member legacy register access commands Parav Pandit
2023-07-07 9:30 ` [virtio-comment] " Michael S. Tsirkin
2023-07-07 13:26 ` [virtio-comment] " Parav Pandit
2023-07-07 14:17 ` [virtio-comment] " Michael S. Tsirkin
2023-07-07 14:18 ` Parav Pandit
2023-07-07 15:32 ` Parav Pandit [this message]
2023-07-07 11:46 ` [virtio-comment] Re: [PATCH v12 0/3] admin: Access legacy registers using admin commands Cornelia Huck
2023-07-07 15:31 ` [virtio-comment] " Parav Pandit
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=PH0PR12MB5481EDC9C3F7D397FCF34AC4DC2DA@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).