All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: "U-Boot Mailing List" <u-boot@lists.denx.de>,
	"Masahiro Yamada" <yamada.masahiro@socionext.com>,
	"Bin Meng" <bmeng.cn@gmail.com>,
	"Marek Behún" <marek.behun@nic.cz>,
	"Pali Rohár" <pali@kernel.org>
Subject: Re: [PATCH] Makefile: Add a warning about ad-hoc CONFIG options
Date: Mon, 20 Sep 2021 11:20:07 -0400	[thread overview]
Message-ID: <20210920152007.GX8579@bill-the-cat> (raw)
In-Reply-To: <20210918182122.1854781-1-sjg@chromium.org>

[-- Attachment #1: Type: text/plain, Size: 637 bytes --]

On Sat, Sep 18, 2021 at 12:21:21PM -0600, Simon Glass wrote:

> 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>

I agree with the sentiment.  But we aren't at the point where even aside
from environment and a few outstanding migrations I've posted but not
yet pulled, that any platform is 100% clean.  There's still even
migrated-but-in-config.h symbols seemingly everywhere.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2021-09-20 15:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-18 18:21 [PATCH] Makefile: Add a warning about ad-hoc CONFIG options Simon Glass
2021-09-20 15:20 ` Tom Rini [this message]
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=20210920152007.GX8579@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=bmeng.cn@gmail.com \
    --cc=marek.behun@nic.cz \
    --cc=pali@kernel.org \
    --cc=sjg@chromium.org \
    --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.