On Sun, Jan 01 2023, Parav Pandit <pa...@nvidia.com> wrote:
> Place device specification, its driver and device
> conformance into its own directory to have self contained device
> specification.
>
> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/153
> Signed-off-by: Parav Pandit <pa...@nvidia.com>
> ---
> changelog:
> v0->v1:
> - new patch
> ---
> conformance.tex | 21 +------------------
> content.tex | 2 +-
> .../virtio-gpio/device-conformance.tex | 9 ++++++++
> .../virtio-gpio/device.tex | 0
> .../virtio-gpio/driver-conformance.tex | 9 ++++++++
> 5 files changed, 20 insertions(+), 21 deletions(-)
> create mode 100644 device-types/virtio-gpio/device-conformance.tex
> rename virtio-gpio.tex => device-types/virtio-gpio/device.tex (100%)
> create mode 100644 device-types/virtio-gpio/driver-conformance.tex
(...)
> @@ -251,16 +242,6 @@ \section{Conformance Targets}\label{sec:Conformance /
> Conformance Targets}
> \import{device-types/virtio-mem/}{device-conformance}
> \import{device-types/virtio-scmi/}{device-conformance}
>
> -\conformance{\subsection}{GPIO Device Conformance}\label{sec:Conformance /
> Device Conformance / GPIO Device Conformance}
> -
> -A General Purpose Input/Output (GPIO) device MUST conform to the following
> -normative statements:
> -
> -\begin{itemize}
> -\item \ref{devicenormative:Device Types / GPIO Device / requestq Operation}
> -\item \ref{devicenormative:Device Types / GPIO Device / eventq Operation}
> -\end{itemize}
> -
Missing
\import{device-types/virtio-gpio/}{device-conformance}
> \conformance{\subsection}{PMEM Device Conformance}\label{sec:Conformance /
> Device Conformance / PMEM Device Conformance}
>
> A PMEM device MUST conform to the following normative statements:
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-h...@lists.oasis-open.org
