From: Harald Mommer <harald.mommer@opensynergy.com>
To: Vincent Mailhol <vincent.mailhol@gmail.com>
Cc: virtio-dev@lists.linux.dev, linux-can@vger.kernel.org,
Wolfgang Grandegger <wg@grandegger.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Dariusz Stojaczyk <Dariusz.Stojaczyk@opensynergy.com>
Subject: Re: [PATCH 1/1] virtio-can: Add link to CAN specification from ISO.
Date: Fri, 7 Jun 2024 15:49:38 +0200 [thread overview]
Message-ID: <5f9dbedc-eeca-4be4-af6b-7d8bf739f89a@opensynergy.com> (raw)
In-Reply-To: <CAMZ6RqK+doMKZfsbchHsfo9xYdEoKGyQk035PHbiW0quWFM+sg@mail.gmail.com>
Got a justified complaint about causing too much noise, so took out
linux-kernel@vger.kernel.org and netdev@vger.kernel.org to shorten the CC.
On 07.06.24 05:43, Vincent Mailhol wrote:
> On Thu. 6 Jun. 2024 at 23:26, Harald Mommer
> <Harald.Mommer@opensynergy.com> wrote:
>> Add link to the CAN specification in the ISO shop.
>>
>> ISO 11898-1:2015
>> Road vehicles
>> Controller area network (CAN)
>> Part 1: Data link layer and physical signalling
>>
>> The specification is not freely obtainable there.
>> ---
>> introduction.tex | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/introduction.tex b/introduction.tex
>> index 8bcef03..72573d6 100644
>> --- a/introduction.tex
>> +++ b/introduction.tex
> Excuse my ignorance, this is not a patch toward the Linux tree, right?
> Could you let me know which git tree this patch is targetting?
targeted to git repository: https://github.com/oasis-tcs/virtio-spec.git
branch: virtio-1.4 (37c6a406678a).
>> @@ -142,7 +142,8 @@ \section{Normative References}\label{sec:Normative References}
>> TRANSMISSION CONTROL PROTOCOL
>> \newline\url{https://ddec1-0-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fwww.rfc%2deditor.org%2frfc%2frfc793%7d%5c%5c&umid=65841137-ddc9-4901-90a4-a0cb61c155d1&auth=53c7c7de28b92dfd96e93d9dd61a23e634d2fbec-04306aba055e4efd56e85e2894cfd163fc39b45a
>> \phantomsection\label{intro:CAN}\textbf{[CAN]} &
>> - ISO 11898-1:2015 Road vehicles -- Controller area network (CAN) -- Part 1: Data link layer and physical signalling\\
>> + ISO 11898-1:2015 Road vehicles -- Controller area network (CAN) -- Part 1: Data link layer and physical signalling
>> + \newline\url{https://ddec1-0-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fwww.iso.org%2fstandard%2f63648.html%7d%5c%5c&umid=65841137-ddc9-4901-90a4-a0cb61c155d1&auth=53c7c7de28b92dfd96e93d9dd61a23e634d2fbec-0151c683df516f2ca3c42192c0ecb6e43e334d9f
>> \end{longtable}
> I just realised that ISO 11898-1:2024 was published last month:
> https://ddec1-0-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fwww.iso.org%2fstandard%2f86384.html&umid=65841137-ddc9-4901-90a4-a0cb61c155d1&auth=53c7c7de28b92dfd96e93d9dd61a23e634d2fbec-3887c3b5f94c9c2790492dc7ef4af9e35b9cc020.
>
> Just for confirmation, are you keeping the reference to ISO
> 11898-1:2015 until CAN XL support gets added? If yes, OK as-is.
Saw also yesterday the update at ISO when checking the link and thought
a moment about it. The now superseded specification 11898-1:2015 is the
one which was used when the virtio CAN specification was developed. So
this is the one to be referenced now.
> On my side, I now need to read the new ISO 11898-1:2024.
On my side, before reading the new ISO 11898-1:2024 it first has to be
ordered and to be delivered.
>> \section{Non-Normative References}
>> --
>> 2.34.1
>>
> >
prev parent reply other threads:[~2024-06-07 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 14:12 [PATCH 1/1] virtio-can: Add link to CAN specification from ISO Harald Mommer
2024-06-07 9:09 ` Michael S. Tsirkin
[not found] ` <CAMZ6RqK+doMKZfsbchHsfo9xYdEoKGyQk035PHbiW0quWFM+sg@mail.gmail.com>
2024-06-07 13:49 ` Harald Mommer [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=5f9dbedc-eeca-4be4-af6b-7d8bf739f89a@opensynergy.com \
--to=harald.mommer@opensynergy.com \
--cc=Dariusz.Stojaczyk@opensynergy.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=vincent.mailhol@gmail.com \
--cc=virtio-dev@lists.linux.dev \
--cc=wg@grandegger.com \
/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