From: Giox79 <giovanniparodi79@gmail.com>
To: linux-can@vger.kernel.org
Subject: Re: CAN j1939 library doubts
Date: Fri, 15 Mar 2013 10:27:04 +0000 (UTC) [thread overview]
Message-ID: <loom.20130315T112433-345@post.gmane.org> (raw)
In-Reply-To: 20130314210751.GC1387@vandijck-laurijssen.be
Kurt Van Dijck <kurt.van.dijck <at> eia.be> writes:
>
> On Thu, Mar 14, 2013 at 04:20:08PM +0000, Giox79 wrote:
> > Kurt Van Dijck <kurt.van.dijck <at> eia.be> writes:
> >
> > In order to integrate your libs to my kernel, I was supposing to make a diff
> > between source file, looking mainly at can and iproute2, merge the diffs and
> > build the whole system.
> > Do you think this is the right approach?
> no. I (just) prepared the repositories to allow easy merges.
>
> follow these steps (@Marc, can you just verify the 'git' calls):
>
> git clone your kernel, or get a stable one
> $ git clone http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git
> ... this takes time
> $ cd linux-stable
> $ git tag
> choose a version, like v3.3, or v3.8, ...
> $ git checkout <chosen-version>
> $ git checkout -b <new-branch-name>
> This last command creates a new branch, so you can play freely.
> Now choose your branch on http://gitorious.org/~kurt-vd/linux-can/linux-can-
j1939
> , like j1939-v3.3
> $ git pull git://gitorious.org/~kurt-vd/linux-can/linux-can-j1939.git
<gitorious-branch-name>
>
> If this all went ok, then you're ready now.
>
> The same applies for can-utils & iproute2.
> You could also clone my j1939 versions directly if you do not care about
> the precise versions, like:
> $ git clone -b <gitorious-branch-name> git://gitorious.org/~kurt-
vd/linux-can/iproute2-j1939
> with <gitorious-branch-name> something like 'j1939-v3.6'.
> In contrast to the kernel, I never modify iproute2 besides j1939 stuff,
> so this would work very fine.
> Even an .tgz export could work then.
>
> Kind regards,
> Kurt
> --
> To unsubscribe from this list: send the line "unsubscribe linux-can" in
> the body of a message to majordomo <at> vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
Kurt, thanks a lot for your great help.
I will give it a try during the weekend, I have to use a customized linux kernel
based on 3.6, so I will apply the suggested steps skipping the git to download
official linux kernel.
I will let you know my tests results. At present time, thanks again and
congratulation for your work.
next prev parent reply other threads:[~2013-03-15 10:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 21:52 CAN j1939 library doubts Giox79
2013-03-13 8:29 ` Jean-Claude Monnin
2013-03-13 8:42 ` Kurt Van Dijck
2013-03-14 11:17 ` Giox79
2013-03-14 12:20 ` Kurt Van Dijck
2013-03-14 16:20 ` Giox79
2013-03-14 21:07 ` Kurt Van Dijck
2013-03-15 10:27 ` Giox79 [this message]
2013-03-15 10:33 ` Marc Kleine-Budde
2013-03-16 9:35 ` Giox79
2013-03-14 11:17 ` Giox79
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=loom.20130315T112433-345@post.gmane.org \
--to=giovanniparodi79@gmail.com \
--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.