From: Cornelia Huck <cohuck@redhat.com>
To: Jiang Wang <jiang.wang@bytedance.com>,
virtio-comment@lists.oasis-open.org
Cc: Jiang Wang <jiang.wang@bytedance.com>
Subject: Re: [virtio-comment] [PATCH v2] virtio-net: fix a display for num_buffers
Date: Thu, 10 Jun 2021 13:00:03 +0200 [thread overview]
Message-ID: <87tum6yogc.fsf@redhat.com> (raw)
In-Reply-To: <20210601172139.3725854-1-jiang.wang@bytedance.com>
On Tue, Jun 01 2021, Jiang Wang <jiang.wang@bytedance.com> wrote:
> One of num_buffers does not display correctly in
> the html. The _b becomes a subscript b. This will
> prevent it from being searched by using keyword num_buffers.
>
> Fix it by adding a field keyword.
>
> Signed-off-by: Jiang Wang <jiang.wang@bytedance.com>
> ---
> v1 -> v2: use field keyword instead of adding an escape char.
>
> content.tex | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Thanks, pushed as an editorial update.
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
prev parent reply other threads:[~2021-06-10 11:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 17:21 [virtio-comment] [PATCH v2] virtio-net: fix a display for num_buffers Jiang Wang
2021-06-10 11:00 ` Cornelia Huck [this message]
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=87tum6yogc.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=jiang.wang@bytedance.com \
--cc=virtio-comment@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