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: [PATCH v1 0/2] Move transitional dev req to legacy interface
Date: Sun, 26 Feb 2023 00:06:34 +0200	[thread overview]
Message-ID: <20230225220636.429990-1-parav@nvidia.com> (raw)

Currently the PCI transitional device discovery requirements
are located in two sections. One it located in regular device
section mixed with non transitional device normative statements.
Some of them are already located in the second legacy interface
section.

Legacy interfaces is the section to describe transitional device
requirements as mentioned in the first legacy interface section
2.2.3.

Hence move these normative statements and requirements to the
Legacy interface section.

This is only an editorial change.

patch summary:
patch-1 use capital alphabets to define device id
patch-2 move pci device id normative statements adjacent to other
requirements

changelog:
1. use lowercase letters
2. add missing '.'

Parav Pandit (2):
  transport-pci: Use lowecase alphabets
  transport-pci: Move transitional device id to legacy section

 transport-pci.tex | 82 ++++++++++++++++++++++++-----------------------
 1 file changed, 42 insertions(+), 40 deletions(-)

-- 
2.26.2


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 v1 0/2] Move transitional dev req to legacy interface
Date: Sun, 26 Feb 2023 00:06:34 +0200	[thread overview]
Message-ID: <20230225220636.429990-1-parav@nvidia.com> (raw)
Message-ID: <20230225220634.sw_tO1Ho1veMRT_DRWLf63rxOoBf5jno8KZO2V9f3mM@z> (raw)

Currently the PCI transitional device discovery requirements
are located in two sections. One it located in regular device
section mixed with non transitional device normative statements.
Some of them are already located in the second legacy interface
section.

Legacy interfaces is the section to describe transitional device
requirements as mentioned in the first legacy interface section
2.2.3.

Hence move these normative statements and requirements to the
Legacy interface section.

This is only an editorial change.

patch summary:
patch-1 use capital alphabets to define device id
patch-2 move pci device id normative statements adjacent to other
requirements

changelog:
1. use lowercase letters
2. add missing '.'

Parav Pandit (2):
  transport-pci: Use lowecase alphabets
  transport-pci: Move transitional device id to legacy section

 transport-pci.tex | 82 ++++++++++++++++++++++++-----------------------
 1 file changed, 42 insertions(+), 40 deletions(-)

-- 
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


             reply	other threads:[~2023-02-25 22:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-25 22:06 Parav Pandit [this message]
2023-02-25 22:06 ` [virtio-dev] [PATCH v1 0/2] Move transitional dev req to legacy interface Parav Pandit
2023-02-25 22:06 ` [PATCH v1 1/2] transport-pci: Use lowecase alphabets Parav Pandit
2023-02-25 22:06   ` [virtio-dev] " Parav Pandit
2023-02-25 22:06 ` [PATCH v1 2/2] transport-pci: Move transitional device id to legacy section Parav Pandit
2023-02-25 22:06   ` [virtio-dev] " Parav Pandit
2023-02-25 22:59   ` Michael S. Tsirkin
2023-02-25 22:59     ` [virtio-dev] " Michael S. Tsirkin
2023-02-27  2:54     ` Parav Pandit
2023-02-27  2:54       ` [virtio-dev] " Parav Pandit
2023-02-27  7:29       ` Michael S. Tsirkin
2023-02-27  7:29         ` [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=20230225220636.429990-1-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