From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Cc: Michael Olbrich <m.olbrich@pengutronix.de>
Subject: [PATCH] common: remove unused CONFIG_BOOTM_OFTREE
Date: Fri, 13 Jun 2025 12:32:15 +0200 [thread overview]
Message-ID: <20250613103215.1500101-1-s.hauer@pengutronix.de> (raw)
CONFIG_BOOTM_OFTREE is entirely unused. Remove this Kconfig option.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
arch/kvx/Kconfig | 1 -
common/Kconfig | 13 +------------
2 files changed, 1 insertion(+), 13 deletions(-)
diff --git a/arch/kvx/Kconfig b/arch/kvx/Kconfig
index bb662e4fd8..285f140f44 100644
--- a/arch/kvx/Kconfig
+++ b/arch/kvx/Kconfig
@@ -4,7 +4,6 @@ config KVX
bool
select 64BIT
select BOOTM
- select BOOTM_OFTREE
select BOOTM_INITRD
select COMMON_CLK
select COMMON_CLK_OF_PROVIDER
diff --git a/common/Kconfig b/common/Kconfig
index 987148847e..468a981f32 100644
--- a/common/Kconfig
+++ b/common/Kconfig
@@ -631,17 +631,6 @@ config BOOTM_INITRD
-r INITRD specify an initrd image
-L ADDR specify initrd load address
-config BOOTM_OFTREE
- bool
- depends on BOOTM
- select OFTREE
- prompt "device tree (oftree) support"
- help
- Add support to pass a device tree (a.k.a Open Firmware Tree, oftree). Adds
- this command line option:
-
- -o DTS specify device tree
-
config BOOTM_UIMAGE
def_bool y
prompt "support the legacy uImage format"
@@ -654,7 +643,7 @@ config BOOTM_UIMAGE
config BOOTM_OFTREE_UIMAGE
bool
prompt "support passing device tree (oftree) uImages"
- depends on BOOTM_OFTREE && BOOTM_UIMAGE
+ depends on BOOTM_UIMAGE
help
Support using oftree uImages. Without this only raw oftree
blobs can be used.
--
2.39.5
next reply other threads:[~2025-06-13 11:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 10:32 Sascha Hauer [this message]
2025-06-13 10:38 ` Sascha Hauer
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=20250613103215.1500101-1-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=m.olbrich@pengutronix.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