public inbox for virtio-comment@lists.linux.dev
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
Cc: virtio-comment@lists.linux.dev, harald.mommer@opensynergy.com
Subject: Re: [PATCH] can: drop a broken conformance link
Date: Fri, 12 Jul 2024 06:49:30 -0400	[thread overview]
Message-ID: <20240712064806-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <ZpEJcaI2D1ETfqkF@fedora>

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.


      reply	other threads:[~2024-07-12 10:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 message]

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=20240712064806-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=harald.mommer@opensynergy.com \
    --cc=mvaralar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox