* [PATCH] can: drop a broken conformance link
@ 2024-07-11 19:03 Michael S. Tsirkin
2024-07-12 10:46 ` Matias Ezequiel Vara Larsen
0 siblings, 1 reply; 3+ messages in thread
From: Michael S. Tsirkin @ 2024-07-11 19:03 UTC (permalink / raw)
To: virtio-comment
CAN device has a single device conformance section, drop
a link to a non-existent section, fixing a Latex error.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
device-types/can/device-conformance.tex | 1 -
1 file changed, 1 deletion(-)
diff --git a/device-types/can/device-conformance.tex b/device-types/can/device-conformance.tex
index f944ffd..3725164 100644
--- a/device-types/can/device-conformance.tex
+++ b/device-types/can/device-conformance.tex
@@ -3,6 +3,5 @@
A CAN device MUST conform to the following normative statements:
\begin{itemize}
-\item \ref{devicenormative:Device Types / CAN Device / Feature bits}
\item \ref{devicenormative:Device Types / CAN Device / Device Operation / CAN Message Transmission}
\end{itemize}
--
MST
^ permalink raw reply related [flat|nested] 3+ messages in thread* Re: [PATCH] can: drop a broken conformance link
2024-07-11 19:03 [PATCH] can: drop a broken conformance link Michael S. Tsirkin
@ 2024-07-12 10:46 ` Matias Ezequiel Vara Larsen
2024-07-12 10:49 ` Michael S. Tsirkin
0 siblings, 1 reply; 3+ messages in thread
From: Matias Ezequiel Vara Larsen @ 2024-07-12 10:46 UTC (permalink / raw)
To: Michael S. Tsirkin; +Cc: virtio-comment, harald.mommer
On Thu, Jul 11, 2024 at 03:03:17PM -0400, Michael S. Tsirkin wrote:
> CAN device has a single device conformance section, drop
> a link to a non-existent section, fixing a Latex error.
>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
> device-types/can/device-conformance.tex | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/device-types/can/device-conformance.tex b/device-types/can/device-conformance.tex
> index f944ffd..3725164 100644
> --- a/device-types/can/device-conformance.tex
> +++ b/device-types/can/device-conformance.tex
> @@ -3,6 +3,5 @@
> A CAN device MUST conform to the following normative statements:
>
> \begin{itemize}
> -\item \ref{devicenormative:Device Types / CAN Device / Feature bits}
> \item \ref{devicenormative:Device Types / CAN Device / Device Operation / CAN Message Transmission}
> \end{itemize}
> --
> MST
>
>
I wonder if authors just forgot the`\devicenormative{}` in 5.20.3
section: `Device Requirements: Feature bits`. I added Harald in CC.
Matias
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [PATCH] can: drop a broken conformance link
2024-07-12 10:46 ` Matias Ezequiel Vara Larsen
@ 2024-07-12 10:49 ` Michael S. Tsirkin
0 siblings, 0 replies; 3+ messages in thread
From: Michael S. Tsirkin @ 2024-07-12 10:49 UTC (permalink / raw)
To: Matias Ezequiel Vara Larsen; +Cc: virtio-comment, harald.mommer
On Fri, Jul 12, 2024 at 12:46:09PM +0200, Matias Ezequiel Vara Larsen wrote:
> On Thu, Jul 11, 2024 at 03:03:17PM -0400, Michael S. Tsirkin wrote:
> > CAN device has a single device conformance section, drop
> > a link to a non-existent section, fixing a Latex error.
> >
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > ---
> > device-types/can/device-conformance.tex | 1 -
> > 1 file changed, 1 deletion(-)
> >
> > diff --git a/device-types/can/device-conformance.tex b/device-types/can/device-conformance.tex
> > index f944ffd..3725164 100644
> > --- a/device-types/can/device-conformance.tex
> > +++ b/device-types/can/device-conformance.tex
> > @@ -3,6 +3,5 @@
> > A CAN device MUST conform to the following normative statements:
> >
> > \begin{itemize}
> > -\item \ref{devicenormative:Device Types / CAN Device / Feature bits}
> > \item \ref{devicenormative:Device Types / CAN Device / Device Operation / CAN Message Transmission}
> > \end{itemize}
> > --
> > MST
> >
> >
>
> I wonder if authors just forgot the`\devicenormative{}` in 5.20.3
> section: `Device Requirements: Feature bits`. I added Harald in CC.
>
> Matias
that section needs to be split up - it seems to list requirements
without saying who the requirement is for.
in fact device requirements here generally need work e.g. they specify
a structure of a request driver submits - that should be a driver
requirement or better moved to a non-conformance section.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-07-12 10:49 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-07-11 19:03 [PATCH] can: drop a broken conformance link Michael S. Tsirkin
2024-07-12 10:46 ` Matias Ezequiel Vara Larsen
2024-07-12 10:49 ` Michael S. Tsirkin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox