From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kurt Van Dijck Subject: [RFC v3 0/6] CAN: add SAE J1939 protocol Date: Mon, 14 Mar 2011 14:20:04 +0100 Message-ID: <20110314132004.GA333@e-circ.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org, netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Return-path: Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: socketcan-core-bounces-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org Errors-To: socketcan-core-bounces-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org List-Id: netdev.vger.kernel.org This series adds SAE J1939 support to the current net-next-2.6. For the rtnetlink operations to work, a 2.6.38-rc1 is required. 1/6: can: extend sockaddr_can to include j1939 members 2/6: can: add rtnetlink support 3/6: can: make struct proto const 4/6: j1939: initial import of SAE J1939 5/6: j1939: add documentation & MAINTAINERS 6/6: iproute2: use CAN & J1939 Still a lot of things probably need explanation... Kind regards, Kurt Van Dijck EIA Electronics