linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Travis <travis@sgi.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	linux-next@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: linux-next:  rr_cpumask tree build failure
Date: Mon, 29 Dec 2008 08:31:38 -0800	[thread overview]
Message-ID: <4958FB6A.1060909@sgi.com> (raw)
In-Reply-To: <20081230025557.89d2565e.sfr@canb.auug.org.au>

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.

Hi Stephen,

This was my fault.  I thought that:

	cpumask: make CONFIG_NR_CPUS always valid.
	From: Rusty Russell <rusty@rustcorp.com.au>

was already present upstream.  This would be the better fix, but as a short
term fix, you can use the following patch.

Thanks,
Mike
---
 drivers/base/cpu.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- linux-2.6-for-ingo.orig/drivers/base/cpu.c
+++ linux-2.6-for-ingo/drivers/base/cpu.c
@@ -133,7 +133,7 @@ print_cpus_func(present);
  */
 static ssize_t print_cpus_kernel_max(struct sysdev_class *class, char *buf)
 {
-	int n = snprintf(buf, PAGE_SIZE-2, "%d\n", CONFIG_NR_CPUS - 1);
+	int n = snprintf(buf, PAGE_SIZE-2, "%d\n", NR_CPUS - 1);
 	return n;
 }
 static SYSDEV_CLASS_ATTR(kernel_max, 0444, print_cpus_kernel_max, NULL);

  reply	other threads:[~2008-12-29 16:31 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 [this message]
2008-12-29 22:52 ` Rusty Russell
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=4958FB6A.1060909@sgi.com \
    --to=travis@sgi.com \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rusty@rustcorp.com.au \
    --cc=sfr@canb.auug.org.au \
    /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).