From: "Michael S. Tsirkin" <mst@redhat.com>
To: virtualization@lists.linux-foundation.org,
Amit Shah <amit.shah@redhat.com>
Subject: Re: [PATCH] virtio-spec: serial: english tweak
Date: Mon, 12 Nov 2012 18:56:54 +0200 [thread overview]
Message-ID: <20121112165654.GA18190@redhat.com> (raw)
In-Reply-To: <20120909121116.GA2972@redhat.com>
On Sun, Sep 09, 2012 at 03:11:16PM +0300, Michael S. Tsirkin wrote:
> "A number of virtqueues are created" seems clearer
> than "the number of virtqueues": it's
> virtqueues that are created not the number.
>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
ping
> ---
>
> I'm not a native english speaker but the below
> seems correct to me. Rusty?
>
> virtio-spec.lyx | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/virtio-spec.lyx b/virtio-spec.lyx
> index d9626a9..a29315c 100644
> --- a/virtio-spec.lyx
> +++ b/virtio-spec.lyx
> @@ -6406,7 +6406,7 @@ If the VIRTIO_CONSOLE_F_MULTIPORT feature is negotiated, the driver can
> spawn multiple ports, not all of which may be attached to a console.
> Some could be generic ports.
> In this case, the control virtqueues are enabled and according to the max_nr_po
> -rts configuration-space value, the appropriate number of virtqueues are
> +rts configuration-space value, an appropriate number of virtqueues are
> created.
> A control message indicating the driver is ready is sent to the host.
> The host can then send control messages for adding new ports to the device.
> --
> MST
next prev parent reply other threads:[~2012-11-12 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-09 12:11 [PATCH] virtio-spec: serial: english tweak Michael S. Tsirkin
2012-09-09 20:58 ` Amit Shah
2012-11-12 16:56 ` Michael S. Tsirkin [this message]
2012-12-04 6:08 ` Amos Kong
2013-01-03 0:15 ` Rusty Russell
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=20121112165654.GA18190@redhat.com \
--to=mst@redhat.com \
--cc=amit.shah@redhat.com \
--cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).