From: Francesco Valla <valla.francesco@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Oliver Hartkopp <socketcan@hartkopp.net>,
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>,
fabio@redaril.me, Linux CAN <linux-can@vger.kernel.org>,
Linux Networking <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] Documentation: networking: document CAN ISO-TP
Date: Fri, 15 Mar 2024 17:36:49 +0100 [thread overview]
Message-ID: <ZfR5IXA9tVHgBTva@fedora> (raw)
In-Reply-To: <ZfPUqOVpF8u5738S@archie.me>
On Fri, Mar 15, 2024 at 11:55:04AM +0700, Bagas Sanjaya wrote:
<snip>
>
> htmldocs build reports new warnings:
>
> /home/bagas/repo/linux-kernel/Documentation/networking/isotp.rst:3: WARNING: Title overline too short.
>
> ====================
> ISO-TP (ISO 15765-2) Transport Protocol
> ====================
> /home/bagas/repo/linux-kernel/Documentation/networking/isotp.rst:275: WARNING: Title underline too short.
>
> Multi-frame transport support
> --------------------------
> /home/bagas/repo/linux-kernel/Documentation/networking/isotp.rst:275: WARNING: Title underline too short.
>
> Multi-frame transport support
> --------------------------
>
> I have applied the fixup:
>
> ---- >8 ----
> diff --git a/Documentation/networking/isotp.rst b/Documentation/networking/isotp.rst
> index d0c49fd1f5c976..a104322ddb6c5e 100644
> --- a/Documentation/networking/isotp.rst
> +++ b/Documentation/networking/isotp.rst
> @@ -1,11 +1,11 @@
> .. SPDX-License-Identifier: (GPL-2.0 OR BSD-3-Clause)
>
> -====================
> +=======================================
> ISO-TP (ISO 15765-2) Transport Protocol
> -====================
> +=======================================
>
> Overview
> -=========================
> +========
>
> ISO-TP, also known as ISO 15765-2 from the ISO standard it is defined in, is a
> transport protocol specifically defined for diagnostic communication on CAN.
> @@ -272,7 +272,7 @@ differ less than this value will be ignored:
> ret = setsockopt(s, SOL_CAN_ISOTP, CAN_ISOTP_RX_STMIN, &stmin, sizeof(stmin));
>
> Multi-frame transport support
> ---------------------------
> +-----------------------------
>
> The ISO-TP stack contained inside the Linux kernel supports the multi-frame
> transport mechanism defined by the standard, with the following contraints:
>
> Thanks.
>
> --
> An old man doll... just what I always wanted! - Clara
Thank you! Fixes (along with some rework) will be applied to the v2.
Regards,
Francesco
next prev parent reply other threads:[~2024-03-15 16:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 22:34 [RFC PATCH 0/1] Documentation: networking: document CAN ISO-TP Francesco Valla
2024-03-13 22:34 ` [PATCH 1/1] " Francesco Valla
2024-03-14 11:20 ` Marc Kleine-Budde
2024-03-14 21:12 ` Francesco Valla
2024-03-15 4:55 ` Bagas Sanjaya
2024-03-15 16:36 ` Francesco Valla [this message]
2024-03-19 12:06 ` Simon Horman
2024-03-20 22:35 ` Francesco Valla
2024-03-21 12:34 ` Simon Horman
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=ZfR5IXA9tVHgBTva@fedora \
--to=valla.francesco@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fabio@redaril.me \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=socketcan@hartkopp.net \
/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