Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: Parav Pandit <parav@nvidia.com>
To: mst@redhat.com, virtio-dev@lists.oasis-open.org, cohuck@redhat.com
Cc: virtio-comment@lists.oasis-open.org, shahafs@nvidia.com,
	Parav Pandit <parav@nvidia.com>
Subject: [virtio-comment] [PATCH 1/2] transport-pci: Use capital alphabets
Date: Sat, 25 Feb 2023 01:12:31 +0200	[thread overview]
Message-ID: <20230224231232.340814-2-parav@nvidia.com> (raw)
In-Reply-To: <20230224231232.340814-1-parav@nvidia.com>

Use capital alphabets to write PCI device id
similar to vendor id and existing device id.

Signed-off-by: Parav Pandit <parav@nvidia.com>
---
 transport-pci.tex | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/transport-pci.tex b/transport-pci.tex
index 0642107..e271d51 100644
--- a/transport-pci.tex
+++ b/transport-pci.tex
@@ -61,7 +61,7 @@ \subsection{PCI Device Discovery}\label{sec:Virtio Transport Options / Virtio Ov
 the PCI Vendor and Device ID of the environment (for informational purposes by the driver).
 
 Non-transitional devices SHOULD have a PCI Device ID in the range
-0x1040 to 0x107f.
+0x1040 to 0x107F.
 Non-transitional devices SHOULD have a PCI Revision ID of 1 or higher.
 Non-transitional devices SHOULD have a PCI Subsystem Device ID of 0x40 or higher.
 
@@ -70,7 +70,7 @@ \subsection{PCI Device Discovery}\label{sec:Virtio Transport Options / Virtio Ov
 
 \drivernormative{\subsubsection}{PCI Device Discovery}{Virtio Transport Options / Virtio Over PCI Bus / PCI Device Discovery}
 Drivers MUST match devices with the PCI Vendor ID 0x1AF4 and
-the PCI Device ID in the range 0x1040 to 0x107f,
+the PCI Device ID in the range 0x1040 to 0x107F,
 calculated by adding 0x1040 to the Virtio Device ID,
 as indicated in section \ref{sec:Device Types}.
 Drivers for device types listed in section \ref{sec:Virtio
@@ -89,7 +89,7 @@ \subsubsection{Legacy Interfaces: A Note on PCI Device Discovery}\label{sec:Virt
 Transitional devices MUST have the PCI Subsystem Device ID
 matching the Virtio Device ID, as indicated in section \ref{sec:Device Types}.
 Transitional devices MUST have the Transitional PCI Device ID in
-the range 0x1000 to 0x103f.
+the range 0x1000 to 0x103F.
 
 This is to match legacy drivers.
 
-- 
2.26.2


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: Parav Pandit <parav@nvidia.com>
To: <mst@redhat.com>, <virtio-dev@lists.oasis-open.org>, <cohuck@redhat.com>
Cc: <virtio-comment@lists.oasis-open.org>, <shahafs@nvidia.com>,
	Parav Pandit <parav@nvidia.com>
Subject: [virtio-dev] [PATCH 1/2] transport-pci: Use capital alphabets
Date: Sat, 25 Feb 2023 01:12:31 +0200	[thread overview]
Message-ID: <20230224231232.340814-2-parav@nvidia.com> (raw)
Message-ID: <20230224231231.VNnYmDrobueJrCAycCmHxgE-oCMrqFLEsuWqeSk-KKE@z> (raw)
In-Reply-To: <20230224231232.340814-1-parav@nvidia.com>

Use capital alphabets to write PCI device id
similar to vendor id and existing device id.

Signed-off-by: Parav Pandit <parav@nvidia.com>
---
 transport-pci.tex | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/transport-pci.tex b/transport-pci.tex
index 0642107..e271d51 100644
--- a/transport-pci.tex
+++ b/transport-pci.tex
@@ -61,7 +61,7 @@ \subsection{PCI Device Discovery}\label{sec:Virtio Transport Options / Virtio Ov
 the PCI Vendor and Device ID of the environment (for informational purposes by the driver).
 
 Non-transitional devices SHOULD have a PCI Device ID in the range
-0x1040 to 0x107f.
+0x1040 to 0x107F.
 Non-transitional devices SHOULD have a PCI Revision ID of 1 or higher.
 Non-transitional devices SHOULD have a PCI Subsystem Device ID of 0x40 or higher.
 
@@ -70,7 +70,7 @@ \subsection{PCI Device Discovery}\label{sec:Virtio Transport Options / Virtio Ov
 
 \drivernormative{\subsubsection}{PCI Device Discovery}{Virtio Transport Options / Virtio Over PCI Bus / PCI Device Discovery}
 Drivers MUST match devices with the PCI Vendor ID 0x1AF4 and
-the PCI Device ID in the range 0x1040 to 0x107f,
+the PCI Device ID in the range 0x1040 to 0x107F,
 calculated by adding 0x1040 to the Virtio Device ID,
 as indicated in section \ref{sec:Device Types}.
 Drivers for device types listed in section \ref{sec:Virtio
@@ -89,7 +89,7 @@ \subsubsection{Legacy Interfaces: A Note on PCI Device Discovery}\label{sec:Virt
 Transitional devices MUST have the PCI Subsystem Device ID
 matching the Virtio Device ID, as indicated in section \ref{sec:Device Types}.
 Transitional devices MUST have the Transitional PCI Device ID in
-the range 0x1000 to 0x103f.
+the range 0x1000 to 0x103F.
 
 This is to match legacy drivers.
 
-- 
2.26.2


---------------------------------------------------------------------
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:[~2023-02-24 23:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-24 23:12 [PATCH 0/2] Move transitional dev req to legacy interface Parav Pandit
2023-02-24 23:12 ` [virtio-dev] " Parav Pandit
2023-02-24 23:12 ` Parav Pandit [this message]
2023-02-24 23:12   ` [virtio-dev] [PATCH 1/2] transport-pci: Use capital alphabets Parav Pandit
2023-02-25 17:45   ` Michael S. Tsirkin
2023-02-25 17:45     ` [virtio-dev] " Michael S. Tsirkin
2023-02-25 21:40     ` [virtio-dev] " Parav Pandit
2023-02-24 23:12 ` [PATCH 2/2] transport-pci: Move transitional device id to legacy section Parav Pandit
2023-02-24 23:12   ` [virtio-dev] " Parav Pandit
2023-02-25 17:26   ` Michael S. Tsirkin
2023-02-25 17:26     ` [virtio-dev] " Michael S. Tsirkin
2023-02-25 21:38     ` Parav Pandit
2023-02-25 21:38       ` [virtio-dev] " Parav Pandit
2023-02-25 22:58       ` Michael S. Tsirkin
2023-02-25 22:58         ` [virtio-dev] " Michael S. Tsirkin
2023-02-27  2:48         ` Parav Pandit
2023-02-27  2:48           ` [virtio-dev] " Parav Pandit
2023-02-27  7:24           ` Michael S. Tsirkin
2023-02-27  7:24             ` [virtio-dev] " Michael S. Tsirkin

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=20230224231232.340814-2-parav@nvidia.com \
    --to=parav@nvidia.com \
    --cc=cohuck@redhat.com \
    --cc=mst@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox