All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 3/6] arm: Move MAX_CPUS to Kconfig
Date: Mon, 3 Oct 2016 15:49:23 -0600	[thread overview]
Message-ID: <CAPnjgZ3VejjmJ+mNaXQ-WzdvCX53q6tWGwqk4di63egnZrGyCA@mail.gmail.com> (raw)
In-Reply-To: <1475270352-17225-4-git-send-email-york.sun@nxp.com>

On 30 September 2016 at 15:19, York Sun <york.sun@nxp.com> wrote:
> Move MAX_CPUS option to Kconfig and clean up existing uses for ARM. This
> option is used by Freescale Layerscape SoCs.
>
> Signed-off-by: York Sun <york.sun@nxp.com>
> ---
>  arch/arm/cpu/armv7/ls102xa/Kconfig                | 11 +++++++++++
>  arch/arm/cpu/armv8/fsl-layerscape/Kconfig         | 13 +++++++++++++
>  arch/arm/include/asm/arch-fsl-layerscape/config.h |  4 ----
>  arch/arm/include/asm/arch-ls102xa/config.h        |  1 -
>  4 files changed, 24 insertions(+), 5 deletions(-)

Reviewed-by: Simon Glass <sjg@chromium.org>

Good start - I suppose we should unify these one day.

  reply	other threads:[~2016-10-03 21:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-30 21:19 [U-Boot] [RFC PATCH 0/6] Move some config macros to Kconfig York Sun
2016-09-30 21:19 ` [U-Boot] [RFC PATCH 1/6] arm: Fix Kconfig for proper display menu York Sun
2016-10-03 21:49   ` Simon Glass
2016-09-30 21:19 ` [U-Boot] [RFC PATCH 2/6] arm: Move FSL_LSCH2 FSL_LSCH3 to Kconfig York Sun
2016-10-03 21:49   ` Simon Glass
2016-09-30 21:19 ` [U-Boot] [RFC PATCH 3/6] arm: Move MAX_CPUS " York Sun
2016-10-03 21:49   ` Simon Glass [this message]
2016-09-30 21:19 ` [U-Boot] [RFC PATCH 4/6] arm: Move SYS_FSL_IFC_BANK_COUNT " York Sun
2016-10-03 21:49   ` Simon Glass
2016-09-30 21:19 ` [U-Boot] [RFC PATCH 5/6] arm: Move FSL_HAS_DP_DDR and NUM_DDR_CONTROLLERS " York Sun
2016-10-03 21:49   ` Simon Glass
2016-09-30 21:19 ` [U-Boot] [RFC PATCH 6/6] arm: Move SYS_FSL_SRDS_* and SYS_HAS_SERDES " York Sun
2016-10-03 21:49   ` Simon Glass

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=CAPnjgZ3VejjmJ+mNaXQ-WzdvCX53q6tWGwqk4di63egnZrGyCA@mail.gmail.com \
    --to=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    /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.