From: Marc Kleine-Budde <mkl@pengutronix.de>
To: 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 17:00:59 +0100 [thread overview]
Message-ID: <513DFFBB.8050406@pengutronix.de> (raw)
In-Reply-To: <20130311153437.GD5114@vandijck-laurijssen.be>
[-- Attachment #1: Type: text/plain, Size: 1477 bytes --]
On 03/11/2013 04:34 PM, Kurt Van Dijck wrote:
> On Mon, Mar 11, 2013 at 04:10:12PM +0100, Marc Kleine-Budde wrote:
>> On 03/11/2013 10:29 AM, Kurt Van Dijck wrote:
>>>
>>>
>>> On Fri, Mar 08, 2013 at 01:51:23PM +0100, Robert Schwebel wrote:
>>>> Hi Kurt,
>>>>
>>>> On Fri, Mar 08, 2013 at 11:05:48AM +0100, Kurt Van Dijck wrote:
>>>>> Could I just mark j1939 as "EXPERIMENTAL" in Kconfig.
>>>>> I think that is what I've seen most for 'unstable concepts'.
>>>>
>>>> EXPERIMENTAL is considered to be deprecated and might be removed from
>>>> the kernel, so I wouldn't go down that road. Staging sounds right.
>>>
>>> I see.
>>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/CodingStyle?id=v3.9-rc2#n549
>>>
>>> Is such thing then appropriate?
>>
>> 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.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2013-03-11 16:01 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 [this message]
2013-03-11 17:20 ` Oliver Hartkopp
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=513DFFBB.8050406@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--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).