From: Ingo Molnar <mingo@elte.hu>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: ppc-dev <linuxppc-dev@ozlabs.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Thomas Gleixner <tglx@linutronix.de>,
linux-next@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: linux-next: cpus4096 tree build failure
Date: Thu, 19 Mar 2009 12:53:42 +0100 [thread overview]
Message-ID: <20090319115342.GA22905@elte.hu> (raw)
In-Reply-To: <200903192137.15209.rusty@rustcorp.com.au>
* Rusty Russell <rusty@rustcorp.com.au> wrote:
> On Thursday 19 March 2009 21:23:00 Stephen Rothwell wrote:
> > From: Stephen Rothwell <sfr@canb.auug.org.au>
> > Date: Thu, 19 Mar 2009 21:35:24 +1100
> > Subject: [PATCH] powerpc: mmzone.h needs cpumask_t to be defined
> >
> > Commit 082edb7bf443eb8eda15b482d16ad9dd8137ad24 ("numa,cpumask: move
> > numa_node_id default implementation to topology.h") removed the include
> > of linux/topology.h from linux/mmzone.h which exposed this lack.
> >
> > Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
>
> Acked-by: Rusty Russell <rusty@rustcorp.com.au>
>
> Ingo, please apply.
>
> Apparently sparc is similarly broken :(
I've applied it.
( I cannot push it to the auto-cpus4096-next branch yet because you
broke the scheduler as well (boot crash) so the topic is marked
broken. )
Ingo
next prev parent reply other threads:[~2009-03-19 11:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 10:53 linux-next: cpus4096 tree build failure Stephen Rothwell
2009-03-19 11:03 ` Stephen Rothwell
2009-03-19 11:54 ` [tip:cpus4096] numa, cpumask: move numa_node_id default implementation to topology.h, fix Stephen Rothwell
2009-03-19 11:07 ` linux-next: cpus4096 tree build failure Rusty Russell
2009-03-19 11:53 ` Ingo Molnar [this message]
2009-03-19 21:22 ` 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=20090319115342.GA22905@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rusty@rustcorp.com.au \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).