All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Philippe Gerum <rpm@xenomai.org>
Cc: Alexis Berlemont <alexis.berlemont@domain.hid>,
	xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Build tests.
Date: Tue, 15 Dec 2009 11:17:06 +0100	[thread overview]
Message-ID: <4B276222.3010900@domain.hid> (raw)
In-Reply-To: <1260871765.2216.102.camel@domain.hid>

Philippe Gerum wrote:
> On Mon, 2009-12-14 at 14:32 +0100, Gilles Chanteperdrix wrote:
>> Hi,
>>
>> I am working on automated build tests of several configurations of
>> Xenomai head. While running them, I found a few issues, and would need
>> acks, since it is in parts others maintain.
>>
>> Alex: https://mail.gna.org/public/xenomai-git/2009-12/msg00112.html
>>
>> Wolfgang: https://mail.gna.org/public/xenomai-git/2009-12/msg00113.html
>>
>> Anyone: https://mail.gna.org/public/xenomai-git/2009-12/msg00114.html
>>
>> Philippe (check powerpc 2.4):
>> https://mail.gna.org/public/xenomai-git/2009-12/msg00115.html
>>
> 
> We have to include asm/mmu.h to get phys_addr_t defined.
> The default declaration of this type for pre-2.6.28 kernels breaks
> 2.6.20. Better rely on phys_addr_t being defined in linux/types.h, or
> specifically in our wrappers for older kernels. What a mess.
> 
> Tested here on blackfin 2.6.3x, x86* 2.6.27-2.6.30, nios2 2.6.3x, ppc
> 2.4.x, 2.6.20, 2.6.3x. You may want to check this against ARM as well.

Ok. Will do.

-- 
                                          Gilles



  reply	other threads:[~2009-12-15 10:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-14 13:32 [Xenomai-core] Build tests Gilles Chanteperdrix
2009-12-14 13:50 ` Jan Kiszka
2009-12-14 13:56   ` Gilles Chanteperdrix
2009-12-14 14:02   ` Wolfgang Grandegger
2009-12-14 22:50 ` Alexis Berlemont
2009-12-15 10:09 ` Philippe Gerum
2009-12-15 10:17   ` Gilles Chanteperdrix [this message]
2009-12-16  8:48   ` 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=4B276222.3010900@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=alexis.berlemont@domain.hid \
    --cc=rpm@xenomai.org \
    --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.