From: Mike Travis <travis@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Gautham R Shenoy <ego@in.ibm.com>, Li Zefan <lizf@cn.fujitsu.com>,
Sergio Luis <sergio@larces.uece.br>,
Suresh Siddha <suresh.b.siddha@intel.com>,
Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>,
Yinghai Lu <Yinghai.Lu@Sun.COM>,
LKML <linux-kernel@vger.kernel.org>,
Jack Steiner <steiner@sgi.com>
Subject: Re: git-pull request for tip/cpus4096
Date: Fri, 02 Jan 2009 10:24:31 -0800 [thread overview]
Message-ID: <495E5BDF.6030204@sgi.com> (raw)
In-Reply-To: <20090102180942.GB10072@elte.hu>
Ingo Molnar wrote:
> * Mike Travis <travis@sgi.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?
As in the bits included in this pull request, or as in the last set of cpumask
changes yet to be pushed to you? (Either is fine with me, just let me know
what you want me to do.)
>
> 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:
I'll leave this to Rusty, as it's his baby. (Is there an echo in here? ;-)
Thanks,
Mike
>
> 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
next prev parent reply other threads:[~2009-01-02 18:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 17:00 git-pull request for tip/cpus4096 Mike Travis
2009-01-02 18:09 ` Ingo Molnar
2009-01-02 18:24 ` Mike Travis [this message]
2009-01-03 6:01 ` Rusty Russell
2009-01-03 6:18 ` Stephen Rothwell
2009-01-03 10:03 ` Rusty Russell
2009-01-03 10:20 ` Stephen Rothwell
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=495E5BDF.6030204@sgi.com \
--to=travis@sgi.com \
--cc=Yinghai.Lu@Sun.COM \
--cc=ego@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=sergio@larces.uece.br \
--cc=steiner@sgi.com \
--cc=suresh.b.siddha@intel.com \
--cc=svaidy@linux.vnet.ibm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox