From: Tom Rini <trini@konsulko.com>
To: Troy Kisky <troykiskyboundary@gmail.com>
Cc: "u-boot@lists.denx.de" <u-boot@lists.denx.de>,
sjg@chromium.org, festevam@gmail.com, marex@denx.de,
gary.bisson@lairdconnect.com
Subject: Re: CONFIG_IS_ENABLED vs IS_ENABLED
Date: Thu, 26 Jan 2023 12:34:43 -0500 [thread overview]
Message-ID: <Y9K5s3BtSMoNGyQg@bill-the-cat> (raw)
In-Reply-To: <CAO46J5WpuY8tsmKgWu0ikkEo5Y-mr0p_nrShxfergM0GVxHNXw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1920 bytes --]
On Thu, Jan 26, 2023 at 09:26:18AM -0800, Troy Kisky wrote:
> Thanks Simon
>
> I switched emails to get rid of the legalese.
> Below are scripts to commit the changes sorted by
> CONFIG_x variable. The only one I know causes a problem
> is CONFIG_OF_LIVE because of
>
> drivers/core/Makefile
> obj-$(CONFIG_$(SPL_)OF_LIVE)
>
> So, that config needs to keep using CONFIG_IS_ENABLED even
> though SPL_OF_LIVE isn't in any Kconfig file.
>
> Maybe something like
> config SPL_OF_LIVE
> bool
>
> can be added to a Kconfig to prevent the bad change.
>
> git grep CONFIG_IS_ENABLED|sed -n -e
> "s/\(CONFIG_IS_ENABLED([0-9a-zA-Z_]*)\)/\n\1\n/gp"| \
> sed -n -r "s/CONFIG_IS_ENABLED\(([0-9a-zA-Z_]+)\)/\1/p" |sort -u|xargs -I
> {} \
> sh -c "git grep -E 'config [ST]PL_{}' | grep -q -E -w '[ST]PL_{}' || { git
> grep -l 'CONFIG_IS_ENABLED({})' | \
> xargs -IFile sh -c \"sed -i
> \\\"s/CONFIG_IS_ENABLED({})/IS_ENABLED(CONFIG_{})/g\\\" File\" ; \
> git commit -a -m\"CONFIG_{}: change CONFIG_IS_ENABLED to IS_ENABLED\"; }"
>
> git grep -w IS_ENABLED|sed -n -e
> "s/\(IS_ENABLED(CONFIG_[0-9a-zA-Z_]*)\)/\n\1\n/gp"| \
> sed -n -r "s/IS_ENABLED\(CONFIG_([0-9a-zA-Z_]+)\)/\1/p" |sort -u|xargs -I
> {} \
> sh -c "git grep -E 'config [ST]PL_{}' | grep -q -E -w '[ST]PL_{}' && { git
> grep -l 'IS_ENABLED(CONFIG_{})' | \
> xargs -IFile sh -c \"sed -i
> \\\"s/IS_ENABLED(CONFIG_{})/CONFIG_IS_ENABLED({})/g\\\" File\" ; \
> git commit -a -m\"CONFIG_{}: change IS_ENABLED to CONFIG_IS_ENABLED\"; }"
>
>
> I compile tested a few boards, but a thorough compile test would be good. I
> hope the above helps someone get a few of the changes in mainline.
Submitting a PR against https://github.com/u-boot/u-boot/ will trigger
an Azure CI run, and so a global build. And adding a test to CI to fail
on new introductions of this would be how to prevent further issues.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-01-26 17:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 17:26 CONFIG_IS_ENABLED vs IS_ENABLED Troy Kisky
2023-01-26 17:34 ` Tom Rini [this message]
2023-01-28 17:25 ` Troy Kisky
2023-01-30 17:18 ` Tom Rini
2023-01-30 18:51 ` Troy Kisky
2023-01-30 19:44 ` Tom Rini
2023-01-30 22:16 ` Troy Kisky
2023-01-31 14:16 ` Simon Glass
-- strict thread matches above, loose matches on Subject: below --
2023-01-24 22:52 Troy Kisky
2023-01-24 23:31 ` Troy Kisky
2023-01-25 1:36 ` Simon Glass
2023-01-26 17:21 ` Tom Rini
2023-01-26 18:04 ` Simon Glass
2023-01-26 18:16 ` Tom Rini
2023-01-26 21:29 ` Simon Glass
2023-01-26 21:33 ` Tom Rini
2023-01-27 14:30 ` 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=Y9K5s3BtSMoNGyQg@bill-the-cat \
--to=trini@konsulko.com \
--cc=festevam@gmail.com \
--cc=gary.bisson@lairdconnect.com \
--cc=marex@denx.de \
--cc=sjg@chromium.org \
--cc=troykiskyboundary@gmail.com \
--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