From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: "virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"pasic@linux.ibm.com" <pasic@linux.ibm.com>,
"cohuck@redhat.com" <cohuck@redhat.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
Shahaf Shuler <shahafs@nvidia.com>
Subject: [virtio-dev] Re: [PATCH v3 0/2] transport-pci: msix register desc improve
Date: Fri, 28 Apr 2023 00:46:09 -0400 [thread overview]
Message-ID: <20230428004335-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <DM8PR12MB54809734DCE2820CA728AFA0DC6B9@DM8PR12MB5480.namprd12.prod.outlook.com>
On Fri, Apr 28, 2023 at 04:10:21AM +0000, Parav Pandit wrote:
> Hi,
>
> > From: virtio-comment@lists.oasis-open.org <virtio-comment@lists.oasis-
> > open.org> On Behalf Of Parav Pandit
> > Sent: Monday, April 24, 2023 11:15 AM
>
> > > LGTM.
> > > Given the amount of back and forth, I guess we should vote.
> > >
> > Ok. created github at [1].
> > Will wait for few more days to ask for vote for any other review comments.
> >
> > [1] https://github.com/oasis-tcs/virtio-spec/issues/169
>
> Can you please raise the ballot for this?
ok if you put in link to lore, not to oasis archive, then
please also include date and subject so people can still locate
it in the oasis archive if they need to.
--
MST
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-04-28 4:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 14:54 [virtio-dev] [PATCH v3 0/2] transport-pci: msix register desc improve Parav Pandit
2023-04-21 14:54 ` [virtio-dev] [PATCH v3 1/2] transport-pci: Improve config msix vector description Parav Pandit
2023-04-21 14:54 ` [virtio-dev] [PATCH v3 2/2] transport-pci: Improve queue msix vector register desc Parav Pandit
2023-04-22 10:10 ` [virtio-dev] Re: [PATCH v3 0/2] transport-pci: msix register desc improve Michael S. Tsirkin
2023-04-24 15:15 ` [virtio-dev] " Parav Pandit
2023-04-28 4:10 ` Parav Pandit
2023-04-28 4:46 ` Michael S. Tsirkin [this message]
2023-04-28 4:47 ` [virtio-dev] " Michael S. Tsirkin
2023-04-28 13:35 ` [virtio-dev] " Parav Pandit
2023-05-10 18:29 ` Parav Pandit
2023-05-19 6:29 ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
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=20230428004335-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=parav@nvidia.com \
--cc=pasic@linux.ibm.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@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