From: Parav Pandit <parav@nvidia.com>
To: <virtio-comment@lists.linux.dev>, <mst@redhat.com>,
<cohuck@redhat.com>, <mvaralar@redhat.com>
Cc: <slp@redhat.com>, <shahafs@nvidia.com>, Parav Pandit <parav@nvidia.com>
Subject: [PATCH] virtio-gpu: Fix missing driver conformance file
Date: Sat, 14 Jun 2025 21:13:02 +0300 [thread overview]
Message-ID: <20250614181302.277794-1-parav@nvidia.com> (raw)
Cited patch in the fixes tag missed to include the driver-conformance
file. Add it.
Fixes: f52fb20cbe38 ("virtio-gpu: support blob alignment information")
Signed-off-by: Parav Pandit <parav@nvidia.com>
---
device-types/gpu/driver-conformance.tex | 8 ++++++++
1 file changed, 8 insertions(+)
create mode 100644 device-types/gpu/driver-conformance.tex
diff --git a/device-types/gpu/driver-conformance.tex b/device-types/gpu/driver-conformance.tex
new file mode 100644
index 0000000..9ef708e
--- /dev/null
+++ b/device-types/gpu/driver-conformance.tex
@@ -0,0 +1,8 @@
+\conformance{\subsection}{GPU Driver Conformance}\label{sec:Conformance / Driver Conformance / GPU Driver Conformance}
+
+A GPU Driver MUST conform to the following normative statements:
+
+\begin{itemize}
+\item \ref{drivernormative:Device Types / GPU Device / Device Operation / Device Operation: controlq}
+\item \ref{drivernormative:Device Types / GPU Device / Device Operation / Device Operation: controlq (3d)}
+\end{itemize}
--
2.34.1
next reply other threads:[~2025-06-14 18:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-14 18:13 Parav Pandit [this message]
2025-06-16 10:30 ` [PATCH] virtio-gpu: Fix missing driver conformance file Matias Ezequiel Vara Larsen
2025-07-08 6:56 ` Parav Pandit
2025-07-08 8:06 ` Matias Ezequiel Vara Larsen
2025-07-08 8:11 ` Parav Pandit
2025-07-08 8:28 ` Matias Ezequiel Vara Larsen
2025-07-08 8:29 ` Parav Pandit
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=20250614181302.277794-1-parav@nvidia.com \
--to=parav@nvidia.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=mvaralar@redhat.com \
--cc=shahafs@nvidia.com \
--cc=slp@redhat.com \
--cc=virtio-comment@lists.linux.dev \
/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.