All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH] Convert CONFIG_SKIP_LOWLEVEL_INIT et al to Kconfig
Date: Fri, 8 Apr 2022 10:58:28 +0200	[thread overview]
Message-ID: <d135bb84-e71c-fd09-354e-0304861ce218@gmx.de> (raw)
In-Reply-To: <20210828011830.13238-1-trini@konsulko.com>



On 8/28/21 03:18, Tom Rini wrote:
> This converts the following to Kconfig:
>     CONFIG_SKIP_LOWLEVEL_INIT
>     CONFIG_SKIP_LOWLEVEL_INIT_ONLY
>
> In order to do this, we need to introduce SPL and TPL variants of these
> options so that we can clearly disable these options only in SPL in some
> cases, and both instances in other cases.
>
> Signed-off-by: Tom Rini <trini@konsulko.com>


Since this patch series 'make menuconfig' does not look good anymore:

     *** Compiler: gcc (Ubuntu 11.2.0-18ubuntu1) 11.2.0 ***
     Architecture select (ARM architecture)  --->
[ ] Skip the calls to certain low level initialization functions
[ ] Skip the calls to certain low level initialization functions
[ ] Skip the calls to certain low level initialization functions
[ ] Skip the call to lowlevel_init during early boot ONLY
[ ] Skip the call to lowlevel_init during early boot ONLY
     ARM architecture  --->
     General setup  --->

Who would be able to understand three entries with the same short text?

Why wouldn't these entries live in "General setup" or some other sub-menu?

(Seen with Bananapro_defconfig)

Best regards

Heinrich

  parent reply	other threads:[~2022-04-08  8:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-28  1:18 [PATCH] Convert CONFIG_SKIP_LOWLEVEL_INIT et al to Kconfig Tom Rini
2021-08-31  2:45 ` Daniel Schwierzeck
2021-08-31  2:48   ` Tom Rini
2021-08-31  3:15     ` Daniel Schwierzeck
2021-08-31 22:10 ` Tom Rini
2022-04-08  8:58 ` Heinrich Schuchardt [this message]
2022-04-08 11:22   ` Tom Rini

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=d135bb84-e71c-fd09-354e-0304861ce218@gmx.de \
    --to=xypron.glpk@gmx.de \
    --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 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.