From: Oleksij Rempel <o.rempel@pengutronix.de>
To: dev.kurt@vandijck-laurijssen.be, mkl@pengutronix.de, wg@grandegger.com
Cc: Oleksij Rempel <o.rempel@pengutronix.de>,
kernel@pengutronix.de, linux-can@vger.kernel.org,
netdev@vger.kernel.org
Subject: [PATCH v1 3/5] can: add socket type for CAN_J1939
Date: Mon, 8 Oct 2018 11:48:34 +0200 [thread overview]
Message-ID: <20181008094836.14080-4-o.rempel@pengutronix.de> (raw)
In-Reply-To: <20181008094836.14080-1-o.rempel@pengutronix.de>
This patch is a preparation for SAE J1939 and adds CAN_J1939
socket type.
Signed-off-by: Kurt Van Dijck <dev.kurt@vandijck-laurijssen.be>
Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
---
include/uapi/linux/can.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/include/uapi/linux/can.h b/include/uapi/linux/can.h
index 0afb7d8e867f..06d92d6be6e6 100644
--- a/include/uapi/linux/can.h
+++ b/include/uapi/linux/can.h
@@ -157,7 +157,8 @@ struct canfd_frame {
#define CAN_TP20 4 /* VAG Transport Protocol v2.0 */
#define CAN_MCNET 5 /* Bosch MCNet */
#define CAN_ISOTP 6 /* ISO 15765-2 Transport Protocol */
-#define CAN_NPROTO 7
+#define CAN_J1939 7 /* SAE J1939 */
+#define CAN_NPROTO 8
#define SOL_CAN_BASE 100
--
2.19.0
next prev parent reply other threads:[~2018-10-08 16:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 9:48 [PATCH v1 0/5] can: add SAE J1939 protocol Oleksij Rempel
2018-10-08 9:48 ` [PATCH v1 1/5] mailmap: update email address Oleksij Rempel
2018-10-08 9:48 ` [PATCH v1 2/5] can: introduce REQUIRED_SIZE macro Oleksij Rempel
2018-10-08 9:48 ` Oleksij Rempel [this message]
2018-10-08 9:48 ` [PATCH v1 4/5] can: extend sockaddr_can to include j1939 members Oleksij Rempel
2018-10-08 9:48 ` [PATCH v1 5/5] can: add support of SAE J1939 protocol Oleksij Rempel
2018-10-30 14:54 ` [PATCH v1 0/5] can: add " 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=20181008094836.14080-4-o.rempel@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=dev.kurt@vandijck-laurijssen.be \
--cc=kernel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).