On Fri, Nov 08, 2019 at 07:56:50AM +0100, Heinrich Schuchardt wrote:
On 11/8/19 2:32 AM, AKASHI Takahiro wrote:
Due to the commit 4b0bcfa7c4ec ("Kconfig: Migrate CONFIG_BOOTM_* options") BOOTEFI and BOOTEFI_HELLO_COMPILE (and other BOOTEFI configs) are displayed in a long distance. This will make it difficult for us to understand that those configurations are closely related.
Signed-off-by: AKASHI Takahiro takahiro.akashi@linaro.org
This is what the change looks like:
== BEFORE ==
[*] bootm [ ] bootz -*- booti [*] bootefi [*] Support booting Linux OS images [*] Support booting NetBSD (non-EFI) loader images [ ] Support booting OPENRTOS / FreeRTOS images [ ] Support booting Enea OSE images [*] Support booting Plan9 OS images [*] Support booting RTEMS OS images [*] Support booting VxWorks OS images [*] Compile a standard EFI hello world binary for testing [ ] Allow booting a standard EFI hello world for testing [*] UEFI unit tests [ ] bootmenu
== AFTER ==
[*] bootm [ ] bootz -*- booti [*] Support booting Linux OS images [*] Support booting NetBSD (non-EFI) loader images [ ] Support booting OPENRTOS / FreeRTOS images [ ] Support booting Enea OSE images [*] Support booting Plan9 OS images [*] Support booting RTEMS OS images [*] Support booting VxWorks OS images [*] bootefi [*] Compile a standard EFI hello world binary for testing [ ] Allow booting a standard EFI hello world for testing [*] UEFI unit tests [ ] bootmenu
Reviewed-by: Heinrich Schuchardt xypron.glpk@gmx.de
Oops, I got things off by an entry, thanks for fixing this.
Reviewed-by: Tom Rini trini@konsulko.com