All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masahiro YAMADA <yamada.m@jp.panasonic.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] Kconfig: Move CONFIG_SYS_MALLOC_F_LEN to Kconfig
Date: Fri, 12 Dec 2014 02:53:23 +0900	[thread overview]
Message-ID: <CAMhH57QVMUYoQJMytb6Ri_cm15KYueQ6E8HG=LvtAhQ9JbFO_g@mail.gmail.com> (raw)
In-Reply-To: <1418131289-829-2-git-send-email-sjg@chromium.org>

Hi Simon,


2014-12-09 22:21 GMT+09:00 Simon Glass <sjg@chromium.org>:
> diff --git a/arch/arm/cpu/armv7/tegra-common/Kconfig b/arch/arm/cpu/armv7/tegra-common/Kconfig
> index 898e86d..9c98d19 100644
> --- a/arch/arm/cpu/armv7/tegra-common/Kconfig
> +++ b/arch/arm/cpu/armv7/tegra-common/Kconfig
> @@ -17,6 +17,9 @@ config TEGRA124
>
>  endchoice
>
> +config SYS_MALLOC_F_LEN
> +       default 0x1800
> +


I do not object against your way now, but it seems unfortunate because
I think this kind of stuff should go to _defconfig.

The problem is that we have much more defconfig files than Linux
without much differences but we do not have something like
tegra-common_defconfig.

I have been thinking of this these days.

Perhaps, one possible solution I have come up with is to use
scripts/kconfig/merge_config.sh
For example,

 -  "make  tegra30_defconfig"  + tegra30_harmony.config   -> Harmony board
 -  "make tegra30_defconfig" + tegra30_seaboard.config    -> Seaboard







-- 
Best Regards
Masahiro Yamada

  reply	other threads:[~2014-12-11 17:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-09 13:21 [U-Boot] [PATCH 1/2] RFC: dm: Kconfig: Move all driver model CONFIGs to Kconfig Simon Glass
2014-12-09 13:21 ` [U-Boot] [PATCH 2/2] Kconfig: Move CONFIG_SYS_MALLOC_F_LEN " Simon Glass
2014-12-11 17:53   ` Masahiro YAMADA [this message]
2014-12-11 18:44     ` Simon Glass
2014-12-11 17:37 ` [U-Boot] [PATCH 1/2] RFC: dm: Kconfig: Move all driver model CONFIGs " Masahiro YAMADA
2015-01-01  0:39   ` Simon Glass
2015-01-27 23:40 ` Joe Hershberger

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='CAMhH57QVMUYoQJMytb6Ri_cm15KYueQ6E8HG=LvtAhQ9JbFO_g@mail.gmail.com' \
    --to=yamada.m@jp.panasonic.com \
    --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.