All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Parav Pandit <parav@nvidia.com>,
	virtio-dev@lists.oasis-open.org,
	virtio-comment@lists.oasis-open.org, shahafs@nvidia.com
Subject: Re: [PATCH v3] virtio-net: Improve introductory description
Date: Thu, 9 Feb 2023 07:31:18 -0500	[thread overview]
Message-ID: <20230209073110-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <877cwr6myi.fsf@redhat.com>

On Thu, Feb 09, 2023 at 01:29:57PM +0100, Cornelia Huck wrote:
> On Thu, Feb 09 2023, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> 
> > On Thu, Feb 09, 2023 at 03:41:08AM +0200, Parav Pandit wrote:
> >> @@ -389,8 +392,8 @@ \subsection{Device Operation}\label{sec:Device Types / Network Device / Device O
> >>  };
> >>  \end{lstlisting}
> >>  
> >> -The controlq is used to control device features such as
> >> -filtering.
> >> +The controlq is used to control many device features described further in
> >
> > many seems subjective.
> >
> > s/many/some of the/ ?
> 
> s/many/various/ instead? That section should cover all of the device
> features controled via the control vq.

I like that.

> >
> >> +section \ref{sec:Device Types / Network Device / Device Operation / Control Virtqueue}.


  reply	other threads:[~2023-02-09 12:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09  1:41 [PATCH v3] virtio-net: Improve introductory description Parav Pandit
2023-02-09 11:38 ` [virtio-comment] " Cornelia Huck
2023-02-09 12:38   ` Parav Pandit
2023-02-09 12:02 ` [virtio-comment] " David Edmondson
2023-02-09 12:45   ` Parav Pandit
2023-02-09 12:48     ` Michael S. Tsirkin
2023-02-09 13:16     ` David Edmondson
2023-02-09 12:18 ` Michael S. Tsirkin
2023-02-09 12:29   ` [virtio-dev] " Cornelia Huck
2023-02-09 12:31     ` Michael S. Tsirkin [this message]
2023-02-09 12:47       ` 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=20230209073110-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=cohuck@redhat.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.