From: Francesco Valla <valla.francesco@gmail.com>
To: 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>
Cc: fabio@redaril.me, linux-can@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Francesco Valla <valla.francesco@gmail.com>
Subject: [RFC PATCH 0/1] Documentation: networking: document CAN ISO-TP
Date: Wed, 13 Mar 2024 23:34:30 +0100 [thread overview]
Message-ID: <20240313223445.87170-1-valla.francesco@gmail.com> (raw)
While the in-kernel 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.
Sending as RFC because my experience with the stack is as user and not
as its developer, and also because it's my first kernel contribution.
Thank you,
Francesco
Francesco Valla (1):
Documentation: networking: document CAN ISO-TP
Documentation/networking/index.rst | 1 +
Documentation/networking/isotp.rst | 347 +++++++++++++++++++++++++++++
2 files changed, 348 insertions(+)
create mode 100644 Documentation/networking/isotp.rst
--
2.44.0
next reply other threads:[~2024-03-13 22:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 22:34 Francesco Valla [this message]
2024-03-13 22:34 ` [PATCH 1/1] Documentation: networking: document CAN ISO-TP 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
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=20240313223445.87170-1-valla.francesco@gmail.com \
--to=valla.francesco@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;
as well as URLs for NNTP newsgroup(s).