admin: Fix requirements wording inconsistencies
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest2 patches 1 replyIn review
- v22 patches 3 repliesSuperseded
- v12 patches 0 repliesSuperseded
Changes in v3 from the cover letter
- Refer to "virtqueue" as such (Stefano Garzarella).
- Narrow down example to have different virtqueues (Stefano Garzarella).
Patches in v3 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | admin: Refer to "no order constraints" only for different queuesadmin.tex | +5 | 1 reply | |
| 2/2 | admin: Fix driver requirement subjectadmin.tex | +1 | 0 replies |
Reviews trailers per patch
All 2 patches have a Reviewed-by or Acked-by.
| Patch | Parav Pandit | Stefano Garzarella |
|---|---|---|
| 1/2 | R-b | |
| 2/2 | R-b | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v3 0/2] admin: Fix requirements wording inconsistencies
I stumbled over some inconsistencies in the administration virtqueue requirements wording. These patches should fix them.
I think they could be considered editorial fixes.
v3:
- Refer to "virtqueue" as such (Stefano Garzarella).
- Narrow down example to have different virtqueues (Stefano Garzarella).
v2:
- Be specific about case without order constraints (Parav Pandit).
Peter Hilber (2):
admin: Refer to "no order constraints" only for different queues
admin: Fix driver requirement subject
admin.tex | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-)
base-commit: 71fe8e907c9d20c53e8327bea99360cb3c529ade
Signature · 1 line
2.43.0