public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH] global: Remove dead code that starts with CONFIG_[0-9A]
Date: Fri, 20 Aug 2021 09:57:56 -0400	[thread overview]
Message-ID: <20210820135756.GE858@bill-the-cat> (raw)
In-Reply-To: <f564f943-03bf-02ea-02c1-74420f17eec6@prevas.dk>

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

On Fri, Aug 20, 2021 at 03:01:19PM +0200, Rasmus Villemoes wrote:
> On 19/08/2021 21.02, Tom Rini wrote:
> > This removes a number of spots of dead code based on symbols that start
> > with CONFIG_[0-9] or CONFIG_A.
> 
> How did you find those symbols? I suppose the actual patch is just
> generated with unifdef or similar.

The entire list is at scripts/config_whitelist.txt and I just used `git
grep -Ovim ...` and removed by hand.

> >  include/configs/vexpress_common.h         |   3 -
> >  14 files changed, 3 insertions(+), 253 deletions(-)
> 
> Shouldn't they also be removed from scripts/config_whitelist.txt ?

I don't bother because there's so many conflicts and it's a generated
by scripts/build-whitelist.sh

> More generally, running
> 
> for x in $(cat scripts/config_whitelist.txt) ; do git grep -w -q $x -- .
> ':!scripts/config_whitelist.txt' || echo $x ; done
> 
> [I'm sure there's a more efficient way...] shows a few symbols that
> could be removed from that file, along with the places where they are
> set via a CONFIG_SYS_EXTRA_OPTIONS.

Yes, finishing the migration of CONFIG_SYS_EXTRA_OPTIONS is also on the
list.  I'm just running down the list looking for chunks of symbols that
hopefully aren't in the categories of:
- Abusing tests for CONFIG_SPL_BUILD to set/unset based on SPL build or
  not.
- Sometimes a value, sometimes a function name.
- Some other kind of game cpp lets you do, but that's not so easy to
  move to Kconfig.

-- 
Tom

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

  reply	other threads:[~2021-08-20 13:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-19 19:02 [PATCH] global: Remove dead code that starts with CONFIG_[0-9A] Tom Rini
2021-08-20 13:01 ` Rasmus Villemoes
2021-08-20 13:57   ` Tom Rini [this message]
2021-08-30 20:59 ` 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=20210820135756.GE858@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=rasmus.villemoes@prevas.dk \
    --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