From: Hemanth Selam <hemanth.selam@gmail.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
"Jason Wang" <jasowangio@gmail.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@oss.qualcomm.com>,
"Xiong Weimin" <xiongweimin@kylinos.cn>
Cc: virtualization@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] vdpa: fix typos in comments
Date: Thu, 5 Nov 2026 12:06:52 +0530 [thread overview]
Message-ID: <cover.1793860522.git.hemanth.selam@gmail.com> (raw)
In-Reply-To: <20261102043526-mutt-send-email-mst@kernel.org>
v1 was a single patch touching both drivers/vdpa/alibaba/eni_vdpa.c and
include/uapi/linux/virtio_net.h. Michael asked for the uapi header to be
split out, and pointed out that the eni_vdpa.c comment also says "ENI is
build upon" where it means "built", so patch 1 now fixes that alongside
the "specfication" it was sent for.
Nothing outside comments changes in either patch.
v1: https://lore.kernel.org/all/20260904104440.18772-1-hemanth.selam@gmail.com/
Hemanth Selam (2):
vdpa: alibaba: fix typos in comment
virtio_net: fix typo in the ANNOUNCE_ACK comment
drivers/vdpa/alibaba/eni_vdpa.c | 2 +-
include/uapi/linux/virtio_net.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
--
2.48.1
next prev parent reply other threads:[~2026-11-05 6:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 10:44 [PATCH] vdpa: fix typos in comments Hemanth Selam
2026-11-02 9:35 ` Michael S. Tsirkin
2026-11-05 6:36 ` Hemanth Selam [this message]
2026-11-05 6:36 ` [PATCH v2 1/2] vdpa: alibaba: fix typos in comment Hemanth Selam
2026-11-05 6:36 ` [PATCH v2 2/2] virtio_net: fix typo in the ANNOUNCE_ACK comment Hemanth Selam
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=cover.1793860522.git.hemanth.selam@gmail.com \
--to=hemanth.selam@gmail.com \
--cc=eperezma@redhat.com \
--cc=jasowangio@gmail.com \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux.dev \
--cc=xiongweimin@kylinos.cn \
--cc=xuanzhuo@linux.alibaba.com \
/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.