From: Mike Travis <travis@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PULL] cpumask tree
Date: Sat, 03 Jan 2009 06:58:47 -0800 [thread overview]
Message-ID: <495F7D27.8020104@sgi.com> (raw)
In-Reply-To: <20090103105208.GA19080@elte.hu>
Ingo Molnar wrote:
> * Rusty Russell <rusty@rustcorp.com.au> wrote:
>
>> On Saturday 03 January 2009 07:08:40 Ingo Molnar wrote:
>>> - architectures that have no __fls (8 out of 21) fail to build:
>>>
>>> arch/cris
>>> arch/frv
>>> arch/h8300
>>> arch/m32r
>>> arch/m68k
>>> arch/mn10300
>>> arch/xtensa
>> Fixes pushed, m68k should be OK tho; is this actual compile test? You have
>> to look in include/asm-m68k to see __fls.
>
> yeah, i stopped the tests after the first two build failures - the rest is
> a grep result from arch/*/, that's why include/asm-m68k/ was left out.
>
>>> Rusty, would it be fine with you if we did all the remaining bits via
>>> tip/cpus4096? It's your tree and your bits and we wanted to send our
>>> remaining bits after your tree went to Linus but the conflict
>>> resolutions from Mike are valuable so i think we should reconsider the
>>> ordering.
>> Yeah, no reason for us to do the merge twice. As long as it ends
>> upstream, I'm a happy camper.
>
> great - lets do it that way then. I have pulled your fixes into the
> cpus4096 tree:
>
> 5ece5c5: xtensa: define __fls
> 5c134da: mn10300: define __fls
> 16a2062: m32r: define __fls
> 9ddabc2: h8300: define __fls
> ee38e51: frv: define __fls
> 0999769: cris: define __fls
>
> Once we have figured out the CPU-hotplug lockdep splat (possibly due to
> Mike's changes not yours) i'll send it to Linus. Thanks,
>
> Ingo
Thanks! Am working on that now.
Mike
next prev parent reply other threads:[~2009-01-03 14:59 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-01 1:19 [PULL] cpumask tree Rusty Russell
2009-01-02 20:06 ` Linus Torvalds
2009-01-02 20:38 ` Ingo Molnar
2009-01-02 23:31 ` Linus Torvalds
2009-01-03 19:38 ` [git pull] cpus4096 tree, part 3 Ingo Molnar
2009-01-03 20:28 ` Linus Torvalds
2009-01-03 20:36 ` Ingo Molnar
2009-01-03 20:56 ` Linus Torvalds
2009-01-03 21:58 ` Ingo Molnar
2009-01-04 3:35 ` Rusty Russell
2009-01-04 4:28 ` Mike Travis
2009-01-03 21:38 ` Ingo Molnar
2009-01-03 22:00 ` Linus Torvalds
2009-01-03 22:37 ` Ingo Molnar
2009-01-05 1:14 ` Nick Piggin
2009-01-05 1:16 ` Nick Piggin
2009-01-26 19:00 ` Andrew Morton
2009-01-26 19:09 ` Linus Torvalds
2009-01-26 19:30 ` Andrew Morton
2009-01-26 20:09 ` Ingo Molnar
2009-01-26 20:44 ` Andrew Morton
[not found] ` <604427e00901261312w23a1f0f5y61fc5c6cc70297fb@mail.gmail.com>
2009-01-26 23:21 ` Ingo Molnar
2009-01-26 23:44 ` Andrew Morton
2009-01-07 17:30 ` Ingo Molnar
2009-01-03 20:58 ` Mike Travis
2009-01-03 7:20 ` [PULL] cpumask tree Rusty Russell
2009-01-03 10:52 ` Ingo Molnar
2009-01-03 11:59 ` [PATCH] ia64: cpumask fix for is_affinity_mask_valid() Ingo Molnar
2009-01-03 12:19 ` [PATCH] cpumask: convert RCU implementations, fix Ingo Molnar
2009-01-04 3:43 ` [PATCH] ia64: cpumask fix for is_affinity_mask_valid() Rusty Russell
2009-01-04 4:20 ` Mike Travis
2009-01-04 12:38 ` Ingo Molnar
2009-01-03 14:58 ` Mike Travis [this message]
2009-01-03 15:06 ` [PULL] cpumask tree Ingo Molnar
2009-01-03 15:31 ` Mike Travis
2009-01-03 15:47 ` Ingo Molnar
2009-01-03 15:52 ` Mike Travis
2009-01-03 16:00 ` Ingo Molnar
2009-01-03 16:09 ` Mike Travis
2009-01-03 16:42 ` Ingo Molnar
2009-01-03 16:48 ` Mike Travis
2009-01-03 17:45 ` Ingo Molnar
2009-01-03 18:13 ` Ingo Molnar
2009-01-03 18:14 ` Mike Travis
2009-01-03 0:23 ` Rusty Russell
2009-01-08 19:10 ` David Daney
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=495F7D27.8020104@sgi.com \
--to=travis@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox