All of lore.kernel.org
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/4] arm64, thunder: Add Kconfig option for Cavium Thunder SoC Family
Date: Fri, 5 Sep 2014 09:39:32 +0100	[thread overview]
Message-ID: <20140905083932.GD13515@arm.com> (raw)
In-Reply-To: <1409903205-2762-2-git-send-email-rric@kernel.org>

On Fri, Sep 05, 2014 at 08:46:42AM +0100, Robert Richter wrote:
> From: Radha Mohan Chintakuntla <rchintakuntla@cavium.com>
> 
> Increase maximum numbers of cpus to 32. This relates to current
> maximal possible cpu number. Increasing this to 64 cpus will be a
> separate patch not part of this enablement patches.

Just out of interest, does raising the current maximum limit actually break
any existing code? If not, then doing this as two patches doesn't seem worth
it.

Will

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Robert Richter <rric@kernel.org>
Cc: Mark Rutland <Mark.Rutland@arm.com>,
	Rob Herring <robh+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
	Catalin Marinas <Catalin.Marinas@arm.com>,
	Radha Mohan Chintakuntla <rchintakuntla@cavium.com>,
	Olof Johansson <olof@lixom.net>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Robert Richter <rrichter@cavium.com>
Subject: Re: [PATCH v2 1/4] arm64, thunder: Add Kconfig option for Cavium Thunder SoC Family
Date: Fri, 5 Sep 2014 09:39:32 +0100	[thread overview]
Message-ID: <20140905083932.GD13515@arm.com> (raw)
In-Reply-To: <1409903205-2762-2-git-send-email-rric@kernel.org>

On Fri, Sep 05, 2014 at 08:46:42AM +0100, Robert Richter wrote:
> From: Radha Mohan Chintakuntla <rchintakuntla@cavium.com>
> 
> Increase maximum numbers of cpus to 32. This relates to current
> maximal possible cpu number. Increasing this to 64 cpus will be a
> separate patch not part of this enablement patches.

Just out of interest, does raising the current maximum limit actually break
any existing code? If not, then doing this as two patches doesn't seem worth
it.

Will

  reply	other threads:[~2014-09-05  8:39 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-05  7:46 [PATCH v2 0/4] arm64, thunder: Enable Cavium Thunder SoC Family Robert Richter
2014-09-05  7:46 ` Robert Richter
2014-09-05  7:46 ` [PATCH v2 1/4] arm64, thunder: Add Kconfig option for " Robert Richter
2014-09-05  7:46   ` Robert Richter
2014-09-05  8:39   ` Will Deacon [this message]
2014-09-05  8:39     ` Will Deacon
2014-09-05  9:21     ` Robert Richter
2014-09-05  9:21       ` Robert Richter
2014-09-05  9:25       ` Will Deacon
2014-09-05  9:25         ` Will Deacon
2014-09-05  9:36         ` Mark Rutland
2014-09-05  9:36           ` Mark Rutland
2014-09-05 10:51           ` Robert Richter
2014-09-05 10:51             ` Robert Richter
2014-09-05  9:32   ` Russell King - ARM Linux
2014-09-05  9:32     ` Russell King - ARM Linux
2014-09-05 10:45     ` Robert Richter
2014-09-05 10:45       ` Robert Richter
2014-09-05 11:05       ` Russell King - ARM Linux
2014-09-05 11:05         ` Russell King - ARM Linux
2014-09-05 12:51         ` Mark Rutland
2014-09-05 12:51           ` Mark Rutland
2014-09-05 14:04           ` Arnd Bergmann
2014-09-05 14:04             ` Arnd Bergmann
2014-09-05 14:22             ` Mark Rutland
2014-09-05 14:22               ` Mark Rutland
2014-09-05 16:25               ` Arnd Bergmann
2014-09-05 16:25                 ` Arnd Bergmann
2014-09-08 11:01                 ` Robert Richter
2014-09-08 11:01                   ` Robert Richter
2014-09-08 12:29                   ` Arnd Bergmann
2014-09-08 12:29                     ` Arnd Bergmann
2014-09-08 18:25                   ` Rob Herring
2014-09-08 18:25                     ` Rob Herring
2014-09-05  7:46 ` [PATCH v2 2/4] arm64, thunder: Add initial dts for Cavium Thunder SoC Robert Richter
2014-09-05  7:46   ` Robert Richter
2014-09-05 11:21   ` Arnd Bergmann
2014-09-05 11:21     ` Arnd Bergmann
2014-09-05 11:21     ` Arnd Bergmann
2014-09-11 14:51     ` Robert Richter
2014-09-11 14:51       ` Robert Richter
2014-09-11 14:51       ` Robert Richter
2014-09-05  7:46 ` [PATCH v2 3/4] arm64, thunder: Document devicetree bindings " Robert Richter
2014-09-05  7:46   ` Robert Richter
2014-09-05  8:42   ` Will Deacon
2014-09-05  8:42     ` Will Deacon
2014-09-05  8:42     ` Will Deacon
2014-09-05  9:32     ` Robert Richter
2014-09-05  9:32       ` Robert Richter
2014-09-05  9:39       ` Mark Rutland
2014-09-05  9:39         ` Mark Rutland
2014-09-05  9:39         ` Mark Rutland
2014-09-08  7:54         ` Robert Richter
2014-09-08  7:54           ` Robert Richter
2014-09-08  7:54           ` Robert Richter
2014-09-05  7:46 ` [PATCH v2 4/4] arm64, defconfig: Enable Cavium Thunder SoC in defconfig Robert Richter
2014-09-05  7:46   ` Robert Richter
2014-09-05  8:42 ` [PATCH v2 0/4] arm64, thunder: Enable Cavium Thunder SoC Family Will Deacon
2014-09-05  8:42   ` Will Deacon

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=20140905083932.GD13515@arm.com \
    --to=will.deacon@arm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.