From: Francesco Valla <valla.francesco@gmail.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>,
Marc Kleine-Budde <mkl@pengutronix.de>,
linux-can@vger.kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Simon Horman <horms@kernel.org>,
Bagas Sanjaya <bagasdotme@gmail.com>,
fabio@redaril.me, Francesco Valla <valla.francesco@gmail.com>
Subject: [PATCH v3 0/1] Documentation: networking: document ISO 15765-2
Date: Fri, 26 Apr 2024 17:18:12 +0200 [thread overview]
Message-ID: <20240426151825.80120-1-valla.francesco@gmail.com> (raw)
While the in-kernel ISO 15765-2 (ISO-TP) stack is fully functional and
easy to use, no documentation exists for it.
This patch adds such documentation, containing the very basics of the
protocol, the APIs and a basic example.
Thanks,
Francesco
---
Changes in v3:
- drop the :2016 version suffix, as in the mean time ISO 15765-2:2024
has been released (and is thus referenced as the referenced
specification)
- add details on mixed addressing (all the paragraph about the addressing
format has been reworked)
- align some descriptions to the specification
- miscellaneous fixes
- collected a Reviewed-by
Changes in v2:
- rename (and re-title) documentation to to align it with KConfig option,
using ISO 15765-2:2016 instead of ISO-TP (the latter is still used for
brevity inside the document)
- address review comments
- solve warnings coming from checkpatch and make htmldocs
Francesco Valla (1):
Documentation: networking: document ISO 15765-2
Documentation/networking/index.rst | 1 +
Documentation/networking/iso15765-2.rst | 386 ++++++++++++++++++++++++
MAINTAINERS | 1 +
3 files changed, 388 insertions(+)
create mode 100644 Documentation/networking/iso15765-2.rst
--
2.44.0
next reply other threads:[~2024-04-26 15:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 15:18 Francesco Valla [this message]
2024-04-26 15:18 ` [PATCH] Documentation: networking: document ISO 15765-2 Francesco Valla
2024-04-27 13:39 ` Vincent MAILHOL
2024-04-29 21:14 ` Francesco Valla
2024-04-29 17:31 ` [PATCH v3 0/1] " Marc Kleine-Budde
2024-04-29 19:18 ` Francesco Valla
2024-04-30 6:13 ` Marc Kleine-Budde
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=20240426151825.80120-1-valla.francesco@gmail.com \
--to=valla.francesco@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=fabio@redaril.me \
--cc=horms@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).