From: "Michael S. Tsirkin" <mst@redhat.com>
To: virtio-comment@lists.oasis-open.org
Cc: Cornelia Huck <cohuck@redhat.com>
Subject: [virtio-comment] [felipe@nutanix.com: [PATCH] content: Fix driver/device wording on ISR bits]
Date: Fri, 20 Nov 2020 10:01:41 -0500 [thread overview]
Message-ID: <20201120100114-mutt-send-email-mst@kernel.org> (raw)
Some kind of technical problem seems to prevent this patch from
getting to list. Forwarding.
----- Forwarded message from Felipe Franciosi <felipe@nutanix.com> -----
Date: Mon, 09 Nov 2020 14:13:18 +0000 (UTC)
From: Felipe Franciosi <felipe@nutanix.com>
To: virtio-comment@lists.oasis-open.org
Cc: mst@redhat.com, Felipe Franciosi <felipe@nutanix.com>
Subject: [PATCH] content: Fix driver/device wording on ISR bits
Message-Id: <20201109141256.152571-1-felipe@nutanix.com>
Section "ISR status capability" incorrectly worded that the bits part of
the register allows the device to distinguish between interrupt types.
It is the driver that needs access to that distinction, not the device.
Signed-off-by: Felipe Franciosi <felipe@nutanix.com>
---
content.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content.tex b/content.tex
index bc26674..3e8effe 100644
--- a/content.tex
+++ b/content.tex
@@ -1040,7 +1040,7 @@ \subsubsection{ISR status capability}\label{sec:Virtio Transport Options / Virti
The \field{offset} for the \field{ISR status} has no alignment requirements.
-The ISR bits allow the device to distinguish between device-specific configuration
+The ISR bits allow the driver to distinguish between device-specific configuration
change interrupts and normal virtqueue interrupts:
\begin{tabular}{ |l||l|l|l| }
--
2.18.4
----- End forwarded message -----
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/
next reply other threads:[~2020-11-20 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 15:01 Michael S. Tsirkin [this message]
2020-11-23 15:39 ` [virtio-comment] Re: [felipe@nutanix.com: [PATCH] content: Fix driver/device wording on ISR bits] 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=20201120100114-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.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 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.