From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 3/3] mkconfig: Do not define CONFIG_SYS_{ARCH, CPU, SOC, VENDOR, BOARD} in config.h.
Date: Tue, 22 Apr 2014 09:42:14 -0600 [thread overview]
Message-ID: <53568DD6.1050404@wwwdotorg.org> (raw)
In-Reply-To: <1398159826-29398-4-git-send-email-yamada.m@jp.panasonic.com>
On 04/22/2014 03:43 AM, Masahiro Yamada wrote:
> This commit modifies mkconfig not to define CONFIG_SYS_ARCH,
> CONFIG_SYS_CPU, CONFIG_SYS_SOC, CONFIG_SYS_VENDOR, CONFIG_SYS_BOARD.
>
> They are still used in some board files.
> Tegra family, OMAP-Panda board, some Samsung boards.
>
> Add CONFIG_SYS_SOC, CONFIG_SYS_BOARD definition to their header files
> to keep the same behavior.
NAK. These are required by include/env_default.h, which creates
environment variables which cross-board boot.scr may use e.g. to create
DTB filenames. These variables need to continue to exist.
next prev parent reply other threads:[~2014-04-22 15:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 9:43 [U-Boot] [RFC PATCH 0/3] Remove CONFIG_SYS_{ARCH, CPU, SOC, VENDOR, BOARD} Masahiro Yamada
2014-04-22 9:43 ` [U-Boot] [RFC PATCH 1/3] env: drop CONFIG_ENV_VARS_UBOOT_CONFIG support Masahiro Yamada
2014-04-22 12:13 ` Wolfgang Denk
2014-04-23 12:03 ` Masahiro Yamada
2014-04-23 16:08 ` Stephen Warren
2014-04-24 1:39 ` Masahiro Yamada
2014-04-23 19:13 ` Wolfgang Denk
2014-04-24 1:19 ` Masahiro Yamada
2014-04-22 9:43 ` [U-Boot] [RFC PATCH 2/3] cmd_pxe: remove SoC, ARCH path from pxe_default_path Masahiro Yamada
2014-04-22 12:55 ` Rob Herring
2014-04-22 15:40 ` Stephen Warren
2014-04-22 9:43 ` [U-Boot] [RFC PATCH 3/3] mkconfig: Do not define CONFIG_SYS_{ARCH, CPU, SOC, VENDOR, BOARD} in config.h Masahiro Yamada
2014-04-22 15:42 ` Stephen Warren [this message]
2014-04-23 7:33 ` Lukasz Majewski
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=53568DD6.1050404@wwwdotorg.org \
--to=swarren@wwwdotorg.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.