From: Simon Glass <sjg@chromium.org>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: "Tom Rini" <trini@konsulko.com>,
"Masahiro Yamada" <yamada.masahiro@socionext.com>,
"Simon Glass" <sjg@chromium.org>, "Bin Meng" <bmeng.cn@gmail.com>,
"Marek Behún" <marek.behun@nic.cz>,
"Pali Rohár" <pali@kernel.org>
Subject: [PATCH] Makefile: Add a warning about ad-hoc CONFIG options
Date: Sat, 18 Sep 2021 12:21:21 -0600 [thread overview]
Message-ID: <20210918182122.1854781-1-sjg@chromium.org> (raw)
The Kconfig feature was added in 2014. Some 7 years later there are still
quite a few CONFIG options that have not been migrated. It is time to
close this out.
Add a deadline and a warning for boards to migrate to Kconfig.
Signed-off-by: Simon Glass <sjg@chromium.org>
---
Makefile | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/Makefile b/Makefile
index 3014788e14e..7e73e6df1ef 100644
--- a/Makefile
+++ b/Makefile
@@ -1132,6 +1132,16 @@ endif
@# know about unless they are in Kconfig. All the existing CONFIG
@# options are whitelisted, so new ones should not be added.
$(call cmd,cfgcheck,u-boot.cfg)
+ @if [ -s include/autoconf.mk ]; then \
+ echo >&2 "===================== WARNING ======================"; \
+ echo >&2 "This board uses ad-hoc CONFIG options, i.e. those"; \
+ echo >&2 "not defined by a Kconfig option."; \
+ echo >&2 "Support for these will be dropped starting with the"; \
+ echo >&2 "v2022.10 release. Please add new Kconfig options"; \
+ echo >&2 "as needed, or use devicetree."; \
+ echo >&2 "Failure to update may result in board removal."; \
+ echo >&2 "===================================================="; \
+ fi
PHONY += dtbs
dtbs: dts/dt.dtb
--
2.33.0.464.g1972c5931b-goog
next reply other threads:[~2021-09-18 18:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-18 18:21 Simon Glass [this message]
2021-09-20 15:20 ` [PATCH] Makefile: Add a warning about ad-hoc CONFIG options Tom Rini
2021-09-21 1:11 ` Simon Glass
2021-09-21 14:49 ` Tom Rini
2021-10-21 20:17 ` 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=20210918182122.1854781-1-sjg@chromium.org \
--to=sjg@chromium.org \
--cc=bmeng.cn@gmail.com \
--cc=marek.behun@nic.cz \
--cc=pali@kernel.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=yamada.masahiro@socionext.com \
/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.