From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Robert Schwebel <r.schwebel@pengutronix.de>,
Sako Youssouf <youssouf.sako@renault-trucks.com>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: Informations About CAN API of the Linux Kernel
Date: Mon, 11 Mar 2013 18:20:07 +0100 [thread overview]
Message-ID: <513E1247.1070405@hartkopp.net> (raw)
In-Reply-To: <513DFFBB.8050406@pengutronix.de>
On 11.03.2013 17:00, Marc Kleine-Budde wrote:
> On 03/11/2013 04:34 PM, Kurt Van Dijck wrote:
>>> Does j1939 have a protocol number? Probably.
>> Yes. 7.
>>
>>> If so, we shouldn't use the
>>> "next free" one for an experimental protocol.
>> That's another reason to have J1939 merged.
>> I would have alerted anyhow when the protocol number 7 got allocated...
>
> Yes, but as soon as you are "officially" using the number 7, you have to
> provide a stable API and ABI to the userspace.
Yep - Additionally i don't think, that reserving the "7" for CAN_J1939 is a
strong reason for pushing the merge process.
We (will say "the Linux CAN community") all know that J1939 is prepared by
Kurt and that we reserve the "7" proto number for it.
I personally see no reason that someone tries to allocate the "7" without our
joint acknowledge.
Regards,
Oliver
prev parent reply other threads:[~2013-03-11 17:20 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2B7D120CFC15DC438D721B998AD9D9E9097105AB@SEGOTNC5180-N2.vcn.ds.volvo.net>
2013-03-06 15:42 ` Informations About CAN API of the Linux Kernel Marc Kleine-Budde
2013-03-06 16:03 ` Sako Youssouf
2013-03-06 16:18 ` Marc Kleine-Budde
2013-03-06 16:25 ` Sako Youssouf
2013-03-06 16:36 ` Marc Kleine-Budde
2013-03-06 16:41 ` Sako Youssouf
2013-03-07 12:40 ` Kurt Van Dijck
2013-03-08 8:55 ` Marc Kleine-Budde
2013-03-08 10:05 ` Kurt Van Dijck
2013-03-08 12:04 ` Oliver Hartkopp
2013-03-08 13:07 ` Kurt Van Dijck
2013-03-08 13:31 ` Kurt Van Dijck
2013-03-08 13:27 ` Yegor Yefremov
2013-03-11 9:31 ` Kurt Van Dijck
2013-03-11 10:03 ` Oliver Hartkopp
2013-03-11 10:21 ` Yegor Yefremov
2013-03-13 14:57 ` Kurt Van Dijck
2013-03-14 8:04 ` Heinz-Jürgen Oertel
2013-03-14 8:28 ` Wolfgang Grandegger
2013-03-14 8:41 ` Heinz-Jürgen Oertel
2013-03-14 10:34 ` Heinz-Jürgen Oertel
2013-03-14 11:00 ` Kurt Van Dijck
2013-03-14 12:25 ` Yegor Yefremov
2013-03-14 12:31 ` Heinz-Jürgen Oertel
2013-03-16 9:48 ` Heinz-Jürgen Oertel
2013-03-08 12:51 ` Robert Schwebel
2013-03-11 9:29 ` Kurt Van Dijck
2013-03-11 15:10 ` Marc Kleine-Budde
2013-03-11 15:34 ` Kurt Van Dijck
2013-03-11 16:00 ` Marc Kleine-Budde
2013-03-11 17:20 ` Oliver Hartkopp [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=513E1247.1070405@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=r.schwebel@pengutronix.de \
--cc=youssouf.sako@renault-trucks.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).