linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linuxppc-dev@lists.ozlabs.org, Anton Blanchard <anton@samba.org>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] pseries: double NR_CPUS in defconfig
Date: Thu, 13 Sep 2012 11:03:40 -0700	[thread overview]
Message-ID: <20120913180340.GH9269@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120913180011.GG9269@linux.vnet.ibm.com>

On 13.09.2012 [11:00:11 -0700], Nishanth Aravamudan wrote:
> Hi Stephen,
> 
> On 13.09.2012 [22:37:39 +1000], Stephen Rothwell wrote:
> > Hi,
> > 
> > On Wed, 12 Sep 2012 10:47:07 -0700 Nishanth Aravamudan <nacc@linux.vnet.ibm.com> wrote:
> > >
> > > Anticipating growth in coming years, we should ensure we are getting
> > > a good lead on testing.
> > 
> > Most changes to pseries_defconfig are copied into ppc64_defconfig.
> > Should this one be as well?
> 
> Ah, I didn't realize that was the case, sorry. Yes, it probably does
> make sense to do this change. Should I just send a follow-on patch?

Actually, ppc64_defconfig doesn't currently define CONFIG_NR_CPUS.
NR_CPUS' powerpc Kconfig allows 2-8192 already, so given the current
state, I'm not sure any further patch is necessary?

Thanks,
Nish

      reply	other threads:[~2012-09-13 18:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12 17:47 [PATCH] pseries: double NR_CPUS in defconfig Nishanth Aravamudan
2012-09-13 12:37 ` Stephen Rothwell
2012-09-13 18:00   ` Nishanth Aravamudan
2012-09-13 18:03     ` Nishanth Aravamudan [this message]

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=20120913180340.GH9269@linux.vnet.ibm.com \
    --to=nacc@linux.vnet.ibm.com \
    --cc=anton@samba.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.org \
    --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).