All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikos Dragazis <ndragazis@arrikto.com>
To: virtio-dev@lists.oasis-open.org
Cc: "Stefan Hajnoczi" <stefanha@redhat.com>,
	"Michael S . Tsirkin" <mst@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: [virtio-dev] [PATCH 10/11] content: Fix typo
Date: Mon, 24 Aug 2020 17:37:07 +0300	[thread overview]
Message-ID: <20200824143708.5664-11-ndragazis@arrikto.com> (raw)
In-Reply-To: <20200824143708.5664-1-ndragazis@arrikto.com>

Signed-off-by: Nikos Dragazis <ndragazis@arrikto.com>
---
 content.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content.tex b/content.tex
index 7541a91..d141e92 100644
--- a/content.tex
+++ b/content.tex
@@ -1550,7 +1550,7 @@ \subsubsection{Device Initialization}\label{sec:Virtio Transport Options / Virti
 Driver MAY fall back on using INT\#x interrupts for a device
 which only supports one MSI-X vector (MSI-X Table Size = 0).
 
-Driver MAY intepret the Table Size as a hint from the device
+Driver MAY interpret the Table Size as a hint from the device
 for the suggested number of MSI-X vectors to use.
 
 Driver MUST NOT attempt to map an event to a vector
-- 
2.17.1


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  parent reply	other threads:[~2020-08-24 14:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-24 14:36 [virtio-dev] [PATCH 00/11] Additional virtio device resources Nikos Dragazis
2020-08-24 14:36 ` [virtio-dev] [PATCH 01/11] content: Remove duplicate content Nikos Dragazis
2020-09-17 15:48   ` [virtio-dev] " Alex Bennée
2020-08-24 14:36 ` [virtio-dev] [PATCH 02/11] content: Minor fix Nikos Dragazis
2020-09-17 16:16   ` [virtio-dev] " Alex Bennée
2020-08-24 14:37 ` [virtio-dev] [PATCH 03/11] content: Update list of virtio cfg structures Nikos Dragazis
2020-09-17 16:34   ` [virtio-dev] " Alex Bennée
2020-09-18 20:24     ` Nikos Dragazis
2020-09-20 14:55       ` Alex Bennée
2020-08-24 14:37 ` [virtio-dev] [PATCH 04/11] content: Minor layout fix Nikos Dragazis
2020-09-17 16:38   ` [virtio-dev] " Alex Bennée
2020-08-24 14:37 ` [virtio-dev] [PATCH 05/11] doorbells: Introduce doorbells Nikos Dragazis
2020-09-17 14:58   ` [virtio-dev] " Alex Bennée
2020-09-17 16:59   ` Alex Bennée
2020-09-17 17:01   ` Alex Bennée
2020-09-18 21:24     ` Nikos Dragazis
2020-08-24 14:37 ` [virtio-dev] [PATCH 06/11] content: Introduce Doorbell cfg type for PCI Nikos Dragazis
2020-08-24 14:37 ` [virtio-dev] [PATCH 07/11] content: Introduce Doorbell register for MMIO Nikos Dragazis
2020-08-24 14:37 ` [virtio-dev] [PATCH 08/11] notifications: Introduce device-specific notifications Nikos Dragazis
2020-08-24 14:37 ` [virtio-dev] [PATCH 09/11] content: Introduce device-specific notification cfg type for PCI Nikos Dragazis
2020-08-24 14:37 ` Nikos Dragazis [this message]
2020-08-24 14:37 ` [virtio-dev] [PATCH 11/11] content: Introduce device-specific notifications for MMIO Nikos Dragazis
2020-09-17 10:19 ` [virtio-dev] Re: [PATCH 00/11] Additional virtio device resources Nikos Dragazis

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=20200824143708.5664-11-ndragazis@arrikto.com \
    --to=ndragazis@arrikto.com \
    --cc=alex.bennee@linaro.org \
    --cc=mst@redhat.com \
    --cc=stefanha@redhat.com \
    --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.