From: "Michael S. Tsirkin" <mst@redhat.com>
To: linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Cc: "Stephen Rothwell" <sfr@canb.auug.org.au>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Jason Wang" <jasowang@redhat.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
virtualization@lists.linux.dev
Subject: [PATCH 1/8] virtio: fix typo in virtio_device_ready() comment
Date: Thu, 13 Nov 2025 04:34:31 -0500 [thread overview]
Message-ID: <db286e9a65449347f6584e68c9960fd5ded2b4b0.1763026134.git.mst@redhat.com> (raw)
In-Reply-To: <cover.1763026134.git.mst@redhat.com>
"coherenct" -> "coherent"
Fixes: 8b4ec69d7e09 ("virtio: harden vring IRQ")
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
include/linux/virtio_config.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/virtio_config.h b/include/linux/virtio_config.h
index 16001e9f9b39..1ea5baa62141 100644
--- a/include/linux/virtio_config.h
+++ b/include/linux/virtio_config.h
@@ -362,7 +362,7 @@ void virtio_device_ready(struct virtio_device *dev)
* specific set_status() method.
*
* A well behaved device will only notify a virtqueue after
- * DRIVER_OK, this means the device should "see" the coherenct
+ * DRIVER_OK, this means the device should "see" the coherent
* memory write that set vq->broken as false which is done by
* the driver when it sees DRIVER_OK, then the following
* driver's vring_interrupt() will see vq->broken as false so
--
MST
next prev parent reply other threads:[~2025-11-13 9:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 9:34 [PATCH 0/8] virtio htmldoc comment fixes Michael S. Tsirkin
2025-11-13 9:34 ` Michael S. Tsirkin [this message]
2025-11-13 9:34 ` [PATCH 2/8] virtio: fix whitespace in virtio_config_ops Michael S. Tsirkin
2025-11-13 9:34 ` [PATCH 3/8] virtio: fix grammar in virtio_queue_info docs Michael S. Tsirkin
2025-11-13 9:34 ` [PATCH 4/8] virtio: fix grammar in virtio_map_ops docs Michael S. Tsirkin
2025-11-13 9:34 ` [PATCH 5/8] virtio: standardize Returns documentation style Michael S. Tsirkin
2025-11-13 9:34 ` [PATCH 6/8] virtio: fix virtqueue_set_affinity() docs Michael S. Tsirkin
2025-11-13 9:34 ` [PATCH 7/8] virtio_ring: fix htmldoc warnings Michael S. Tsirkin
2025-11-13 9:34 ` [PATCH 8/8] virtio: fix map ops comment Michael S. Tsirkin
2025-11-14 0:59 ` [PATCH 0/8] virtio htmldoc comment fixes Jason Wang
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=db286e9a65449347f6584e68c9960fd5ded2b4b0.1763026134.git.mst@redhat.com \
--to=mst@redhat.com \
--cc=corbet@lwn.net \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=virtualization@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®