From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Stephan Kappertz <stephan.kappertz@kabelmail.de>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Ipipe pre and post patch for AM335x beagleBone/ koenkooi branch
Date: Mon, 11 Feb 2013 08:54:23 +0100 [thread overview]
Message-ID: <5118A3AF.60707@xenomai.org> (raw)
In-Reply-To: <9EFD9D88-FCCB-489A-9DA9-06A8C8AFE8EA@kabelmail.de>
On 01/31/2013 03:17 PM, Stephan Kappertz wrote:
>
>>> Hi All,
>>>
>>> sorry for the long delay. As Gilles suggested I have prepared a pre and post patch for ipipe-core-3.2.21-arm-4 and the git repository supporting BeagleBone here: https://github.com/koenkooi/linux/tree/linux-ti33x-psp-3.2.21-r13g%2Bgitr720e07b4c1f687b61b147b31c698cb6816d72f01 . Should I send the patches to the list?
>>>
>>> - Stephan
>>
>> I think that you should.
>>
>> Goran
>>
>
> Here they are.
> Usage:
>
> * clone git repository https://github.com/koenkooi/linux/tree/linux-ti33x-psp-3.2.21-r13g%2Bgitr720e07b4c1f687b61b147b31c698cb6816d72f01
I get:
fatal:
https://github.com/koenkooi/linux/tree/linux-ti33x-psp-3.2.21-r13g%2Bgitr720e07b4c1f687b61b147b31c698cb6816d72f01/info/refs
not found: did you run git update-server-info on the server?
At this point.
--
Gilles.
next prev parent reply other threads:[~2013-02-11 7:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.0.1359630001.19052.xenomai@xenomai.org>
2013-01-31 14:17 ` [Xenomai] Ipipe pre and post patch for AM335x beagleBone/ koenkooi branch Stephan Kappertz
2013-01-31 16:01 ` Michael Haberler
2013-01-31 20:13 ` Stephan Kappertz
2013-01-31 18:52 ` Michael Haberler
2013-02-04 13:28 ` Stephan Kappertz
2013-02-11 7:54 ` Gilles Chanteperdrix [this message]
2013-02-11 8:24 ` Stephan Kappertz
2013-02-11 12:43 ` Gilles Chanteperdrix
2013-01-30 9:21 Stephan Kappertz
2013-01-31 10:38 ` Goran Jakovljevic
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=5118A3AF.60707@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=stephan.kappertz@kabelmail.de \
--cc=xenomai@xenomai.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.