From: Jiri Pirko <jiri@nvidia.com>
To: Parav Pandit <parav@nvidia.com>
Cc: mst@redhat.com, virtio-dev@lists.oasis-open.org,
cohuck@redhat.com, virtio-comment@lists.oasis-open.org,
shahafs@nvidia.com
Subject: Re: [virtio-comment] [PATCH] virtio-net: Fix virtqueues spelling error
Date: Mon, 13 Mar 2023 11:04:48 +0100 [thread overview]
Message-ID: <ZA71QFjxiV8bDDSa@nanopsycho> (raw)
In-Reply-To: <20230310150519.115090-1-parav@nvidia.com>
Fri, Mar 10, 2023 at 04:05:19PM CET, parav@nvidia.com wrote:
>Correct spelling from virtqueus to virtqueues.
>
>Signed-off-by: Parav Pandit <parav@nvidia.com>
Reviewed-by: Jiri Pirko <jiri@nvidia.com>
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/
WARNING: multiple messages have this Message-ID (diff)
From: Jiri Pirko <jiri@nvidia.com>
To: Parav Pandit <parav@nvidia.com>
Cc: mst@redhat.com, virtio-dev@lists.oasis-open.org,
cohuck@redhat.com, virtio-comment@lists.oasis-open.org,
shahafs@nvidia.com
Subject: [virtio-dev] Re: [virtio-comment] [PATCH] virtio-net: Fix virtqueues spelling error
Date: Mon, 13 Mar 2023 11:04:48 +0100 [thread overview]
Message-ID: <ZA71QFjxiV8bDDSa@nanopsycho> (raw)
In-Reply-To: <20230310150519.115090-1-parav@nvidia.com>
Fri, Mar 10, 2023 at 04:05:19PM CET, parav@nvidia.com wrote:
>Correct spelling from virtqueus to virtqueues.
>
>Signed-off-by: Parav Pandit <parav@nvidia.com>
Reviewed-by: Jiri Pirko <jiri@nvidia.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-03-13 10:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 15:05 [virtio-comment] [PATCH] virtio-net: Fix virtqueues spelling error Parav Pandit
2023-03-10 15:05 ` [virtio-dev] " Parav Pandit
2023-03-11 21:18 ` [virtio-comment] " Michael S. Tsirkin
2023-03-11 21:18 ` [virtio-dev] " Michael S. Tsirkin
2023-03-13 10:04 ` Jiri Pirko [this message]
2023-03-13 10:04 ` [virtio-dev] Re: [virtio-comment] " Jiri Pirko
2023-03-15 11:17 ` [virtio-comment] " Cornelia Huck
2023-03-15 11:17 ` [virtio-dev] " 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=ZA71QFjxiV8bDDSa@nanopsycho \
--to=jiri@nvidia.com \
--cc=cohuck@redhat.com \
--cc=mst@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.