linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tyler.baker@linaro.org (Tyler Baker)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: multi_v7_defconfig, sunxi_defconfig: increase maximum number of CPUs
Date: Tue, 10 Feb 2015 19:52:26 -0800	[thread overview]
Message-ID: <1423626748-1277-1-git-send-email-tyler.baker@linaro.org> (raw)

Hello,

I have recently been reviewing the kernel warnings generated from the kernelci.org boot farm, and have discovered that the HiP04 and a80-optimus boards have more CPUs then the maximum allowed in a few of the ARM defconfigs. This series fixes those warnings by increasing the maximum number of CPUs. I went ahead and boot tested these patches on various boards [1] to insure there are no regressions introduced when increasing the number of CPUs. 

Any comments would be appreciated. Perhaps we may want to increase these limits further?

Thanks,

[1] http://kernelci.org/boot/all/job/tbaker/kernel/v3.19-rc4-845-g9f29e39a74a2/ 

Tyler Baker (2):
  ARM: multi_v7_defconfig: increase the number of maximum number of CPUs to
    16
  ARM: sunxi_defconfig: increase the number of maximum number of CPUs to 8

 arch/arm/configs/multi_v7_defconfig | 2 +-
 arch/arm/configs/sunxi_defconfig    | 1 +
 2 files changed, 2 insertions(+), 1 deletion(-)

-- 
2.1.4

             reply	other threads:[~2015-02-11  3:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-11  3:52 Tyler Baker [this message]
2015-02-11  3:52 ` [PATCH 1/2] ARM: multi_v7_defconfig: increase the number of maximum number of CPUs to 16 Tyler Baker
2015-02-11  3:52 ` [PATCH 2/2] ARM: sunxi_defconfig: increase the number of maximum number of CPUs to 8 Tyler Baker
2015-02-16 12:59   ` Maxime Ripard
2015-03-04 22:43 ` [PATCH 0/2] ARM: multi_v7_defconfig, sunxi_defconfig: increase maximum number of CPUs Arnd Bergmann
2015-03-04 22:46   ` Tyler Baker
  -- strict thread matches above, loose matches on Subject: below --
2015-02-11  3:51 Tyler Baker

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=1423626748-1277-1-git-send-email-tyler.baker@linaro.org \
    --to=tyler.baker@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).