public inbox for virtio-comment@lists.linux.dev
 help / color / mirror / Atom feed
From: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
To: "Michael S. Tsirkin" <mst@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 12:46:09 +0200	[thread overview]
Message-ID: <ZpEJcaI2D1ETfqkF@fedora> (raw)
In-Reply-To: <87a6c3c4463e9f304cdd5dd5fac2194a95a8bcd2.1720724591.git.mst@redhat.com>

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


  reply	other threads:[~2024-07-12 10:46 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 [this message]
2024-07-12 10:49   ` Michael S. Tsirkin

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=ZpEJcaI2D1ETfqkF@fedora \
    --to=mvaralar@redhat.com \
    --cc=harald.mommer@opensynergy.com \
    --cc=mst@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