All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Dinesh Velayudham <Dinesh.Velayutham@LnTtechservices.com>,
	gianluca <gianlucarenzi@eurek.it>,
	"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: J1939 Linux
Date: Thu, 14 Apr 2016 12:49:59 +0200	[thread overview]
Message-ID: <570F75D7.6000708@pengutronix.de> (raw)
In-Reply-To: <20160414100314.GB16018@airbook.vandijck-laurijssen.be>


[-- Attachment #1.1: Type: text/plain, Size: 721 bytes --]

On 04/14/2016 12:03 PM, Kurt Van Dijck wrote:
> I pushed j1939d-v3.19.
> 
> I created the branch by merging & cherry-pick, as suggested earlier.
> I didn't have compile problems.
> 
> I have not tested it, yet I foresee no problems, or at least no
> differences compared to my other j1939d-vx.xx branches.

I want to do the first steps of mainlining j1939. Which is the preferred
branch? I've started with j1939/j1939d-v4.3.

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: 455 bytes --]

  reply	other threads:[~2016-04-14 10:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05 15:43 J1939 Linux Dinesh
2016-04-06  7:46 ` Kurt Van Dijck
2016-04-06 14:33   ` Dinesh Velayudham
2016-04-06 19:40     ` Kurt Van Dijck
2016-04-07 22:28       ` Dinesh Velayudham
2016-04-08  9:04         ` Kurt Van Dijck
2016-04-08 11:20           ` gianluca
2016-04-08 11:58             ` Kurt Van Dijck
2016-04-08 14:29               ` Dinesh Velayudham
2016-04-09 11:40                 ` Kurt Van Dijck
     [not found]                   ` <03B271BE48E2554EB34508DAB79DBABA8709986A@POCITMSEXMB05.LntUniverse.com>
     [not found]                     ` <20160412082020.GA19875@airbook.vandijck-laurijssen.be>
     [not found]                       ` <03B271BE48E2554EB34508DAB79DBABA8709A50F@POCITMSEXMB05.LntUniverse.com>
2016-04-12 18:15                         ` Kurt Van Dijck
2016-04-12 18:28                           ` Dinesh Velayudham
2016-04-13 16:08                           ` Dinesh Velayudham
2016-04-13 18:33                             ` Kurt Van Dijck
2016-04-14 10:03                             ` Kurt Van Dijck
2016-04-14 10:49                               ` Marc Kleine-Budde [this message]
2016-04-14 12:22                                 ` Kurt Van Dijck
2016-04-14 12:31                                   ` Marc Kleine-Budde
2016-04-14 15:51                                     ` Kurt Van Dijck
2016-04-14 17:52                               ` Dinesh Velayudham
2016-04-14 23:10                                 ` Kurt Van Dijck

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=570F75D7.6000708@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=Dinesh.Velayutham@LnTtechservices.com \
    --cc=gianlucarenzi@eurek.it \
    --cc=linux-can@vger.kernel.org \
    /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.