Move transitional dev req to legacy interface
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 7 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | transport-pci: Use capital alphabetstransport-pci.tex | +3 | 2 replies | |
| 2/2 | transport-pci: Move transitional device id to legacy sectiontransport-pci.tex | +36 | 5 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] Move transitional dev req to legacy interface
Currently, the PCI transitional device discovery requirements are located in two sections. One it located in the 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.
It is on top of series [1].
[1] https://lists.oasis-open.org/archives/virtio-dev/202302/msg00578.html
patch summary:
patch-1 use capital alphabets to define device id patch-2 move pci device id normative statements adjacent to other requirements
Parav Pandit (2):
transport-pci: Use capital alphabets
transport-pci: Move transitional device id to legacy section
transport-pci.tex | 74 ++++++++++++++++++++++++----------------------- 1 file changed, 38 insertions(+), 36 deletions(-)
Signature · 1 line
2.26.2