linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: sathnaga@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org
Cc: Satheesh Rajendran <sathnaga@linux.vnet.ibm.com>
Subject: Re: powerpc: Add CONFIG_NR_CPUS to ppc64_defconfig
Date: Tue, 27 Nov 2018 20:22:28 +1100 (AEDT)	[thread overview]
Message-ID: <433yx02JJRz9sBh@ozlabs.org> (raw)
In-Reply-To: <20181108102518.32612-1-sathnaga@linux.vnet.ibm.com>

On Thu, 2018-11-08 at 10:25:18 UTC, sathnaga@linux.vnet.ibm.com wrote:
> From: Satheesh Rajendran <sathnaga@linux.vnet.ibm.com>
> 
> CONFIG_NR_CPUS is not set in ppc64_defconfig, So
> it gets default to 32 which is not likely suitable for
> powerpc systems configuration, hence defaulting it to 2048
> like other powerpc defconfigs.
> 
> Signed-off-by: Satheesh Rajendran <sathnaga@linux.vnet.ibm.com>

Applied to powerpc next, thanks.

https://git.kernel.org/powerpc/c/2f40d82fef1ccad05ea5d99dbd8db5

cheers

      reply	other threads:[~2018-11-27  9:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 10:25 [PATCH] powerpc: Add CONFIG_NR_CPUS to ppc64_defconfig sathnaga
2018-11-27  9:22 ` Michael Ellerman [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=433yx02JJRz9sBh@ozlabs.org \
    --to=patch-notifications@ellerman.id.au \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=sathnaga@linux.vnet.ibm.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).