All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: Cornelia Huck <cohuck@redhat.com>,
	"virtio-dev@lists.oasis-open.org"
	<virtio-dev@lists.oasis-open.org>,
	"virtio-comment@lists.oasis-open.org"
	<virtio-comment@lists.oasis-open.org>,
	Shahaf Shuler <shahafs@nvidia.com>,
	David Edmondson <david.edmondson@oracle.com>
Subject: Re: [PATCH v6] virtio-net: Improve introductory description
Date: Thu, 16 Feb 2023 10:49:52 -0500	[thread overview]
Message-ID: <20230216104714-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB5481F4E1099DF88D667DBD2CDCA09@PH0PR12MB5481.namprd12.prod.outlook.com>

On Thu, Feb 16, 2023 at 02:30:03PM +0000, Parav Pandit wrote:
> 
> > From: Cornelia Huck <cohuck@redhat.com>
> > Sent: Thursday, February 16, 2023 9:10 AM
> > 
> > On Tue, Feb 14 2023, Parav Pandit <parav@nvidia.com> wrote:
> > 
> > > The control VQ of the virtio network device is used beyond advance
> > > steering control. The control VQ dynamically changes multiple features
> > > of the initialized device.
> > >
> > > Hence, update this area of control VQ introductory description at few
> > > places and also place the link to its description.
> > >
> > > Also update the introduction section to better describe receive and
> > > transmit virtqueues.
> > >
> > > Fixes: https://github.com/oasis-tcs/virtio-spec/issues/156
> > > Reviewed-by: David Edmondson <david.edmondson@oracle.com>
> > > Signed-off-by: Parav Pandit <parav@nvidia.com>
> > 
> > Are you requesting a vote for this?
> 
> I was not sure if its need voting as most are editorial cleanups, better description, structure movement.
> Please advise if we need voting.


The bylaws are here:
https://github.com/oasis-tcs/virtio-spec/blob/master/README.md
Minor cleanups, including editorial formatting changes, spelling and
typo fixes can be committed directly into git for approval as part of
the next specification approval ballot.

This is way beyond that. And generally when in doubt vote.

-- 
MST


  reply	other threads:[~2023-02-16 15:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14 18:04 [PATCH v6] virtio-net: Improve introductory description Parav Pandit
2023-02-16 14:09 ` [virtio-comment] " Cornelia Huck
2023-02-16 14:30   ` Parav Pandit
2023-02-16 15:49     ` Michael S. Tsirkin [this message]
2023-02-16 16:00       ` [virtio-comment] " Parav Pandit
2023-02-16 16:02         ` Parav Pandit
2023-02-16 16:03       ` [virtio-comment] " Cornelia Huck
2023-02-16 16:05         ` [virtio-comment] " Parav Pandit
2023-02-16 16:30           ` [virtio-dev] " Cornelia Huck
2023-02-17  2:59             ` Parav Pandit
2023-02-20 13:34               ` [virtio-comment] " Cornelia Huck

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=20230216104714-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=david.edmondson@oracle.com \
    --cc=parav@nvidia.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 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.