From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH 00/16] Kconfig: Tidy up the top-level kconfig menu
Date: Fri, 11 Sep 2020 12:11:06 -0400 [thread overview]
Message-ID: <20200911161106.GR7259@bill-the-cat> (raw)
In-Reply-To: <20200911022127.3451713-1-sjg@chromium.org>
On Thu, Sep 10, 2020 at 08:21:11PM -0600, Simon Glass wrote:
>
> At present this menu is pretty messy, with quite a few minor options shown
> at the top level. This series creates a few new menus and moves things
> around so that the top-level menu is cleaner.
>
> There is more to do, but this is a start.
[snip]
> Kconfig | 340 +---------------
> cmd/Kconfig | 117 ------
> common/Kconfig | 505 ++----------------------
> common/Kconfig.boot | 894 +++++++++++++++++++++++++++++++++++++++++++
> drivers/core/Kconfig | 11 +
> dts/Kconfig | 9 -
> env/Kconfig | 9 +
> tools/Kconfig | 12 +
> 8 files changed, 955 insertions(+), 942 deletions(-)
> create mode 100644 common/Kconfig.boot
> create mode 100644 tools/Kconfig
And after a resync of the defconfigs:
555 files changed, 941 insertions(+), 941 deletions(-)
and a partial wc -l:
449 Kconfig
697 common/Kconfig
894 common/Kconfig.boot
2190 cmd/Kconfig
So in the end, yes, this is I think making things easier to maintain but
will cause a few merge hiccups.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200911/7e80ee44/attachment.sig>
next prev parent reply other threads:[~2020-09-11 16:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 2:21 [PATCH 00/16] Kconfig: Tidy up the top-level kconfig menu Simon Glass
2020-09-11 2:21 ` [PATCH 01/16] Kconfig: Add a 'Boot options' menu Simon Glass
2020-09-11 2:21 ` [PATCH 02/16] Kconfig: Move boot menu into common/ Simon Glass
2020-09-11 2:21 ` [PATCH 03/16] Kconfig: Move boot timing under boot options Simon Glass
2020-09-11 2:21 ` [PATCH 04/16] Kconfig: Move boot media " Simon Glass
2020-09-11 2:21 ` [PATCH 05/16] Kconfig: Move autoboot options " Simon Glass
2020-09-11 2:21 ` [PATCH 06/16] Kconfig: Move CONFIG_BOOTDELAY under autoboot options Simon Glass
2020-09-11 2:21 ` [PATCH 07/16] Kconfig: Move misc boot options under 'boot options' Simon Glass
2020-09-11 2:21 ` [PATCH 08/16] Kconfig: Move SUPPORT_RAW_INITRD under boot options Simon Glass
2020-09-11 2:21 ` [PATCH 09/16] Kconfig: Move DEFAULT_FDT_FILE " Simon Glass
2020-09-11 2:21 ` [PATCH 10/16] Kconfig: Create a new 'init options' menu Simon Glass
2020-09-11 2:21 ` [PATCH 11/16] Kconfig: Move startup hooks under init options Simon Glass
2020-09-11 2:21 ` [PATCH 12/16] Kconfig: MISC_INIT_R and BOARD_LATE_INIT -> start-up hooks Simon Glass
2020-09-11 2:21 ` [PATCH 13/16] Kconfig: Move VERSION_VARIABLE under environment Simon Glass
2020-09-11 2:21 ` [PATCH 14/16] Kconfig: Move BOUNCE_BUFFER under driver options Simon Glass
2020-09-11 2:21 ` [PATCH 15/16] Kconfig: Move BOARD_TYPES under init options Simon Glass
2020-09-11 2:21 ` [PATCH 16/16] Kconfig: Create a new tools menu Simon Glass
2020-09-11 16:11 ` Tom Rini [this message]
2020-09-11 20:15 ` [PATCH 00/16] Kconfig: Tidy up the top-level kconfig menu Simon Glass
2020-09-11 20:20 ` Tom Rini
2020-10-09 22:11 ` 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=20200911161106.GR7259@bill-the-cat \
--to=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