From: Stefano Babic <sbabic@denx.de>
To: Tom Rini <trini@konsulko.com>, Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Stefano Babic <sbabic@denx.de>
Subject: Re: [PATCH 2/3] buildman: Detect Kconfig loops
Date: Thu, 21 Oct 2021 18:35:24 +0200 [thread overview]
Message-ID: <29921036-f02b-dd8f-4d67-520f02eb2a35@denx.de> (raw)
In-Reply-To: <20211021161554.GD3577824@bill-the-cat>
Hi Simon,
On 21.10.21 18:15, Tom Rini wrote:
> On Thu, Oct 21, 2021 at 10:09:56AM -0600, Simon Glass wrote:
>> Hi Tom,
>>
>> On Thu, 21 Oct 2021 at 06:13, Tom Rini <trini@konsulko.com> wrote:
>>>
>>> On Tue, Oct 19, 2021 at 09:43:24PM -0600, Simon Glass wrote:
>>>
>>>> Hex and int Kconfig options are supposed to have defaults. This is so we
>>>> can configure U-Boot without having to enter particular values for the
>>>> items that don't have specific values in the board's defconfig file.
>>>
>>> That's not true. All symbols that we can make reasonable defaults for
>>> get them. It's just that for boolean n is a reasonable default.
>>> int/hex often just need to be entered, period.
>>>
>>> Everything else is fine however, thanks for digging in to this.
>>
>> I got that from there and it made sense as to why we have this problem:
>>
>> https://docs.zephyrproject.org/2.4.0/guides/kconfig/tips.html#redundant-defaults
>
> Yeah, we're just in the bad spot because of things not being fully
> migrated.
>
>> But I think you are right if we should update the commit message here
>> to avoid confusion. Shall I send v2?
>
> Yes please.
As delta...
I applied 1-2 to u-boot-imx (else I was stuck), and they are already
merged as part of my PR. Your patches are already on -master.
Regards,
Stefano
--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@denx.de
=====================================================================
next prev parent reply other threads:[~2021-10-21 16:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 3:43 [PATCH 1/3] buildman: Write output even on fatal error Simon Glass
2021-10-20 3:43 ` [PATCH 2/3] buildman: Detect Kconfig loops Simon Glass
2021-10-21 12:13 ` Tom Rini
2021-10-21 16:09 ` Simon Glass
2021-10-21 16:15 ` Tom Rini
2021-10-21 16:35 ` Stefano Babic [this message]
2021-10-22 3:06 ` 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=29921036-f02b-dd8f-4d67-520f02eb2a35@denx.de \
--to=sbabic@denx.de \
--cc=sjg@chromium.org \
--cc=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).