public inbox for virtio-dev@lists.linux.dev
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.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-dev] Re: [PATCH v6 0/4] admin: Introduce legacy registers access using AQ
Date: Mon, 19 Jun 2023 11:18:34 -0400	[thread overview]
Message-ID: <20230619111731-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB54815F02CE10368D6204EC8CDC5FA@PH0PR12MB5481.namprd12.prod.outlook.com>

On Mon, Jun 19, 2023 at 12:38:29PM +0000, Parav Pandit wrote:
> Hi Michael,
> 
> > From: Parav Pandit <parav@nvidia.com>
> > Sent: Tuesday, June 13, 2023 1:30 PM
> > 
> > This short series introduces legacy registers access commands for the owner
> > group member PCI PF to access the legacy registers of the member VFs.
> > 
> 
> [..]
> 
> > Fixes: https://github.com/oasis-tcs/virtio-spec/issues/167
> > Signed-off-by: Parav Pandit <parav@nvidia.com>
> > 
> > ---
> > changelog:
> > v5->v6:
> > - fixed previous missed abbreviation of LCC and LD
> > - added text for the PCI capability for the group member device
> > v4->v5:
> > - split pci transport and generic command section to new patch
> > - removed multiple references to the VF
> > - written the description of the command as generic with member
> >   and group device terminology
> > - reflected many section names to remove VF
> > - split from pci transport specific patch
> > - split conformance to transport and generic sections
> > - written the description of the command as generic with member
> >   and group device terminology
> > - reflected many section names to remove VF
> > - rename fields from register to region
> > - avoided abbreviation for legacy, device and config
> 
> Do you have any further comments?
> I would like to raise for the vote now as this is in oven for several months now and users need this in 1.3 spec.
> If there are any editorial fixes, I can fix them now with v7 or 
> if they are small, I can fix them during the voting wait period like how we completed AQ fixes.
> Please let me know.


Just back from travel. I remember having comments, will send in a day or
two. I don't think we are talking about editorial things though.


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  reply	other threads:[~2023-06-19 15:18 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13 17:30 [virtio-dev] [PATCH v6 0/4] admin: Introduce legacy registers access using AQ Parav Pandit
2023-06-13 17:30 ` [virtio-dev] [PATCH v6 1/4] admin: Split opcode table rows with a line Parav Pandit
2023-06-13 17:30 ` [virtio-dev] [PATCH v6 2/4] admin: Fix section numbering Parav Pandit
2023-06-13 17:30 ` [virtio-dev] [PATCH v6 3/4] admin: Add group member legacy register access commands Parav Pandit
2023-06-19 16:20   ` [virtio-dev] " Michael S. Tsirkin
2023-06-19 16:29     ` [virtio-dev] " Parav Pandit
2023-06-19 16:40       ` [virtio-dev] " Michael S. Tsirkin
2023-06-19 16:45         ` [virtio-dev] " Parav Pandit
2023-06-19 17:10           ` [virtio-dev] " Michael S. Tsirkin
2023-06-19 17:21             ` Parav Pandit
2023-06-19 17:33               ` Michael S. Tsirkin
2023-06-19 17:38                 ` Parav Pandit
2023-06-13 17:30 ` [virtio-dev] [PATCH v6 4/4] transport-pci: Introduce group legacy group member config region access Parav Pandit
2023-06-19 16:16   ` [virtio-dev] " Michael S. Tsirkin
2023-06-19 21:07     ` [virtio-dev] " Parav Pandit
2023-06-21 20:05       ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-06-21 20:22         ` [virtio-dev] " Parav Pandit
2023-06-21 20:31           ` [virtio-dev] " Michael S. Tsirkin
2023-06-21 20:43             ` [virtio-dev] " Parav Pandit
2023-06-19 16:37   ` [virtio-dev] " Michael S. Tsirkin
2023-06-19 16:39     ` [virtio-dev] " Parav Pandit
2023-06-19 17:19       ` [virtio-dev] " Michael S. Tsirkin
2023-06-19 17:26         ` [virtio-dev] " Parav Pandit
2023-06-19 17:37           ` [virtio-dev] " Michael S. Tsirkin
2023-06-19 17:45             ` [virtio-dev] " Parav Pandit
2023-06-19 17:57               ` [virtio-dev] " Michael S. Tsirkin
2023-06-19 18:07                 ` [virtio-dev] " Parav Pandit
2023-06-20 14:12                   ` Parav Pandit
2023-06-21 15:50                     ` Parav Pandit
2023-06-21 15:56                       ` [virtio-dev] " Michael S. Tsirkin
2023-06-21 16:01                         ` [virtio-dev] " Parav Pandit
2023-06-21 19:43                           ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-06-21 20:04                             ` [virtio-dev] " Parav Pandit
2023-06-21 20:08                               ` [virtio-dev] " Michael S. Tsirkin
2023-06-19 18:00               ` [virtio-dev] " Michael S. Tsirkin
2023-06-19 18:12                 ` [virtio-dev] " Parav Pandit
2023-06-21 19:47                   ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-06-19 17:04   ` [virtio-dev] " Michael S. Tsirkin
2023-06-19 17:11     ` Parav Pandit
2023-06-19 17:26       ` Michael S. Tsirkin
2023-06-19 17:35         ` Parav Pandit
2023-06-19 17:46           ` Michael S. Tsirkin
2023-06-20  0:14             ` Parav Pandit
2023-06-20 10:21               ` Michael S. Tsirkin
2023-06-21  1:09                 ` Parav Pandit
2023-06-21  5:05                   ` Michael S. Tsirkin
2023-06-19 12:38 ` [virtio-dev] RE: [PATCH v6 0/4] admin: Introduce legacy registers access using AQ Parav Pandit
2023-06-19 15:18   ` Michael S. Tsirkin [this message]
2023-06-19 15:58     ` Parav Pandit
2023-06-19 16:28 ` [virtio-dev] " 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=20230619111731-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=david.edmondson@oracle.com \
    --cc=jasowang@redhat.com \
    --cc=maorg@nvidia.com \
    --cc=parav@nvidia.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