From: Rusty Russell <rusty@rustcorp.com.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Mike Travis <travis@sgi.com>
Subject: Re: linux-next: rr_cpumask tree build failure
Date: Tue, 30 Dec 2008 09:22:08 +1030 [thread overview]
Message-ID: <200812300922.08889.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20081230025557.89d2565e.sfr@canb.auug.org.au>
On Tuesday 30 December 2008 02:25:57 Stephen Rothwell wrote:
> Hi Rusty,
>
> Today's linux-next build (powerpc allnoconfig) failed like this:
>
> drivers/base/cpu.c: In function 'print_cpus_kernel_max':
> drivers/base/cpu.c:136: error: 'CONFIG_NR_CPUS' undeclared (first use in this function)
>
> Caused by commit e057d7aea9d8f2a46cd440d8bfb72245d4e72d79 ("cpumask: add
> sysfs displays for configured and disabled cpu maps") from the rr_cpumask
> tree. Powerpc (at least) does not define CONFIG_NR_CPUS for a non SMP
> build.
>
> I have reverted that commit for today.
Thanks, we defined that in a later patch which hadn't been put in the cpumask
tree yet. I've moved it (and several others) in now.
Thanks,
Rusty.
next prev parent reply other threads:[~2008-12-29 22:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 15:55 linux-next: rr_cpumask tree build failure Stephen Rothwell
2008-12-29 16:31 ` Mike Travis
2008-12-29 22:52 ` Rusty Russell [this message]
2008-12-29 23:34 ` 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=200812300922.08889.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=travis@sgi.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;
as well as URLs for NNTP newsgroup(s).