[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090102180942.GB10072@elte.hu>
Date: Fri, 2 Jan 2009 19:09:42 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Mike Travis <travis@....com>
Cc: Rusty Russell <rusty@...tcorp.com.au>,
Gautham R Shenoy <ego@...ibm.com>,
Li Zefan <lizf@...fujitsu.com>,
Sergio Luis <sergio@...ces.uece.br>,
Suresh Siddha <suresh.b.siddha@...el.com>,
Vaidyanathan Srinivasan <svaidy@...ux.vnet.ibm.com>,
Yinghai Lu <Yinghai.Lu@....COM>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: git-pull request for tip/cpus4096
* Mike Travis <travis@....com> wrote:
>
> Hi Ingo,
>
> Here's the latest cpumask updates which includes the latest merge from
> Rusty's cpumask tree.
Pulled into tip/cpus4096, thanks Mike.
Rusty already sent the pull request to Linus for his latest cpumask bits -
is it fine if that goes upstream first and we do the second phase of the
cpus4096 tree after that point?
Also, while testing tip/master i noticed that a couple of architectures
wouldnt build due to cpumask changes:
testing 21 architectures.
testing cris: -git: pass ( 28), -tip: FAIL ( 25)
testing m32r: -git: pass ( 21), -tip: FAIL ( 31)
both build failures go like this:
/home/mingo/tip/lib/find_last_bit.c: In function 'find_last_bit':
/home/mingo/tip/lib/find_last_bit.c:38: error: implicit declaration of function '__fls'
make[2]: *** [lib/find_last_bit.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [lib] Error 2
these architectures have no __fls() implementation ...
trouble should be expected on ~8 architectures:
for N in arch/*; do [ -d $N ] && ( printf "%-20s: " $N; cd $N; dgrep __fls |
wc -l; ); done | sort -t: -n -k +2
arch/cris : 0
arch/frv : 0
arch/h8300 : 0
arch/m32r : 0
arch/m68k : 0
arch/mn10300 : 0
arch/um : 0
arch/xtensa : 0
arch/arm : 1
arch/avr32 : 1
arch/blackfin : 1
arch/ia64 : 1
arch/m68knommu : 1
arch/parisc : 1
arch/powerpc : 1
arch/s390 : 1
arch/sh : 1
arch/x86 : 1
arch/alpha : 2
arch/sparc : 2
arch/mips : 5
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists