All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Flavio Castro Alves Filho <flavio.alves@gmail.com>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] Stable update for ipipe-3.8
Date: Mon, 17 Jun 2013 07:29:45 +0200	[thread overview]
Message-ID: <51BE9EC9.5090408@web.de> (raw)
In-Reply-To: <CAFNBftfCrsdrbgkfzAr5ngJtYJ2PvPtJZAA1ZdBAongHAdO4xw@mail.gmail.com>

On 2013-06-17 02:17, Flavio Castro Alves Filho wrote:
> Hello Jan,
> 
> I tried to build Linux kerne from your ipipe repository but the
> compilation crashed, when building for BeagleBone Black.
> 
> During the patch application, I got just one error, with the inclusion
> of a #include directive. I solved the problem by hand and then I had
> the compilation error.

Err, what did you apply against which kernel? The repository is supposed
to be used as-is. Or are there still additional, non-upstream patches
required for your board?

Jan

> 
> Unfortunately I had to reboot my machine and I could not give you the
> complete feedback. I intend to do that tomorrow. Sorry ...
> 
> Anyway, I would like to provide the feedback.
> 
> Best regards
> 
> Flavio
> 
> 
> 2013/6/12 Flavio Castro Alves Filho <flavio.alves@gmail.com>:
>> Hello,
>>
>> This weekend I'll try to test it with the current kernel version for
>> BeagleBone Black and I'll let you know about the results.
>>
>> Best regards,
>>
>> Flavio
>>
>>
>> 2013/6/11 Jan Kiszka <jan.kiszka@siemens.com>:
>>> Hi all,
>>>
>>> I've merged 3.8.13 into our stable 3.8 branch. This triggered some minor
>>> conflicts in generic and ARM code. Please see
>>>
>>> git://git.xenomai.org/ipipe-jki for-upstream/3.8
>>>
>>> for details. The result works fine for x86, and if it's also OK for the
>>> other arch, I'd propose this to be merged into the official 3.8 stable
>>> branch.
>>>
>>> Jan
>>>
>>> --
>>> Siemens AG, Corporate Technology, CT RTC ITP SES-DE
>>> Corporate Competence Center Embedded Linux
>>>
>>> _______________________________________________
>>> Xenomai mailing list
>>> Xenomai@xenomai.org
>>> http://www.xenomai.org/mailman/listinfo/xenomai
>>
>>
>>
>> --
>> Flavio de Castro Alves Filho
>>
>> flavio.alves@gmail.com
>> www.linuxembarcado.com
>> Twitter: http://twitter.com/#!/fraviofii
>> LinkedIn profile: www.linkedin.com/in/flaviocastroalves
> 
> 
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://www.xenomai.org/pipermail/xenomai/attachments/20130617/0a5f70ef/attachment.pgp>

  reply	other threads:[~2013-06-17  5:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-11 14:28 [Xenomai] Stable update for ipipe-3.8 Jan Kiszka
2013-06-12 14:26 ` Flavio Castro Alves Filho
2013-06-12 15:02   ` Michael Haberler
2013-06-12 17:10     ` Flavio Castro Alves Filho
2013-06-17  0:17   ` Flavio Castro Alves Filho
2013-06-17  5:29     ` Jan Kiszka [this message]
2013-06-19  0:14       ` Flavio Castro Alves Filho
2013-06-22  1:43         ` Flavio Castro Alves Filho
2013-06-22  6:38           ` Jan Kiszka
2013-07-20 11:32 ` Gilles Chanteperdrix
2013-07-26 16:41   ` Jan Kiszka
2013-07-26 17:51     ` Jan Kiszka
2013-07-26 19:11     ` Gilles Chanteperdrix
2013-08-06 19:11     ` Gilles Chanteperdrix

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=51BE9EC9.5090408@web.de \
    --to=jan.kiszka@web.de \
    --cc=flavio.alves@gmail.com \
    --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.