From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Clean all defconfigs with savedefconfig
Date: Mon, 11 May 2015 15:07:14 -0600 [thread overview]
Message-ID: <55511A02.5050809@wwwdotorg.org> (raw)
In-Reply-To: <CANr=Z=bJ4jiT3MTZALMz2J=F1XpSv8_NiA3KbeZFoq1_YjdJWw@mail.gmail.com>
On 05/11/2015 02:17 PM, Joe Hershberger wrote:
> Hi Stephen,
>
> On Mon, May 11, 2015 at 3:02 PM, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> On 05/11/2015 11:08 AM, Joe Hershberger wrote:
>>>
>>> In order to reduce merge conflicts and to maintain the simplest possible
>>> defconfig files, we should be using the savedefconfig feature of Kconfig
>>> every time a new feature is added. This keeps the defconfig settings to
>>> a minimum (only those things not default) and keeps them in the same
>>> order as the Kconfig options.
>>
>>
>>> diff --git a/configs/jetson-tk1_defconfig b/configs/jetson-tk1_defconfig
>>
>>
>>> -CONFIG_TARGET_JETSON_TK1=y
>>
>>
>> Doesn't that (and the equivalent change in other files such as
>> harmony_defconfig) break the build, since the Kconfig option that selects
>> the particular board is no longer selected?
>
> That's a bit of a peculiar case caused by the fact that Kconfig sees
> that board as the default board, so it removes the explicit setting.
>
> The only problem I see with that is if a new board is added to the top
> of the list. We can maybe fix this by changing all of the menus of
> boards to optional, but I'm not sure that's what we want either.
I certainly think we want to make the defconfig files not change
semantics if someone adds a new board earlier in the list, or otherwise
changes the sort order.
Right now, the defconfig files do this by explicitly containing an entry
for the board to build for, even if it's the default in Kconfig. that's
at least simple, but interacts badly with savedefconfig.
Perhaps we can modify e.g. arch/arm/mach-tegra/tegra124/Kconfig (and all
other Kconfig files with choices like this, i.e. choices that are more
than simply a different value that's selected but rather change the
whole meaning of the build target) to explicitly set the default. That
way, if the order of choice entries changes, the defconfig won't change
meaning. For example:
choice
prompt "Tegra124 board select"
# Do not change this value without editing the defconfig for the
# board that the current default. You'd need to add e.g.:
# CONFIG_TARGET_JETSON_TK1=y to that file.
default TARGET_JETSON_TK1
next prev parent reply other threads:[~2015-05-11 21:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 17:08 [U-Boot] [PATCH] Clean all defconfigs with savedefconfig Joe Hershberger
2015-05-11 18:32 ` Joe Hershberger
2015-05-12 15:18 ` Tom Rini
2015-05-12 16:20 ` Joe Hershberger
2015-05-12 16:32 ` Tom Rini
2015-05-13 1:24 ` Masahiro Yamada
2015-05-13 3:33 ` Joe Hershberger
2015-05-11 20:02 ` Stephen Warren
2015-05-11 20:17 ` Joe Hershberger
2015-05-11 21:07 ` Stephen Warren [this message]
2015-05-12 4:19 ` Joe Hershberger
2015-05-12 18:01 ` [U-Boot] [PATCH v2 1/2] kconfig: Make board selection choices optional Joe Hershberger
2015-05-12 18:01 ` [U-Boot] [PATCH v2 2/2] Clean all defconfigs with savedefconfig Joe Hershberger
2015-05-12 19:31 ` [U-Boot] [PATCH v2 1/2] kconfig: Make board selection choices optional Stephen Warren
2015-05-12 19:34 ` Joe Hershberger
2015-05-12 19:46 ` [U-Boot] [PATCH v3 1/2] arch: " Joe Hershberger
2015-05-12 19:46 ` [U-Boot] [PATCH v3 2/2] Clean all defconfigs with savedefconfig Joe Hershberger
2015-05-12 22:12 ` Tom Rini
2015-06-01 7:45 ` Chen-Yu Tsai
2015-06-01 9:46 ` Ian Campbell
2015-06-01 13:41 ` Joe Hershberger
2015-06-01 14:12 ` Tom Rini
2015-05-12 21:55 ` [U-Boot] [PATCH v3 1/2] arch: Make board selection choices optional Stephen Warren
2015-05-12 22:06 ` Joe Hershberger
2015-05-12 22:12 ` Tom Rini
2015-05-13 1:11 ` Masahiro Yamada
2015-07-29 17:25 ` Alexey Brodkin
2015-07-29 17:32 ` Alexey Brodkin
2015-08-01 7:46 ` Masahiro Yamada
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=55511A02.5050809@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox