All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@grandegger.com>
To: "Heinz-Jürgen Oertel" <hj.oertel@t-online.de>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
	Oliver Hartkopp <socketcan@hartkopp.net>,
	Yegor Yefremov <yegorslists@googlemail.com>,
	Kurt Van Dijck <kurt.van.dijck@eia.be>
Subject: Re: Informations About CAN API of the Linux Kernel
Date: Thu, 14 Mar 2013 09:28:25 +0100	[thread overview]
Message-ID: <51418A29.2080705@grandegger.com> (raw)
In-Reply-To: <3528617.Hh7sgC6DGv@linux-edhj>

On 03/14/2013 09:04 AM, Heinz-Jürgen Oertel wrote:
> Am Montag 11 März 2013, 11:03:46 schrieb Oliver Hartkopp:
>> It's hard to check the ML archives so i really would appreciate to have a
>> general overview about SocketCAN and it's dedicated projects.
>>
>> http://elinux.org/CAN_Bus looks to be a good place for that.
> 
> While the idea to collect information in a more structured way is very good,
> I see that we split resources with a new CAN wiki site.
> http://www.can-wiki.info exists
> and
> http://www.can-wiki.info/doku.php?id=can_higher_layer_protocols:j1939

Why not using the Wiki interface of https://gitorious.org/linux-can?

Wolfgang.



  reply	other threads:[~2013-03-14  8:34 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 [this message]
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

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=51418A29.2080705@grandegger.com \
    --to=wg@grandegger.com \
    --cc=hj.oertel@t-online.de \
    --cc=kurt.van.dijck@eia.be \
    --cc=linux-can@vger.kernel.org \
    --cc=socketcan@hartkopp.net \
    --cc=yegorslists@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.