From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH v2 1/2] treewide: Fix wrong CONFIG_IS_ENABLED() handling
Date: Wed, 14 Oct 2020 13:43:24 -0400 [thread overview]
Message-ID: <20201014174324.GL14816@bill-the-cat> (raw)
In-Reply-To: <20201005065730.9768-1-alpernebiyasak@gmail.com>
On Mon, Oct 05, 2020 at 09:57:29AM +0300, Alper Nebi Yasak wrote:
> CONFIG_IS_ENABLED() takes the kconfig name without the CONFIG_ prefix,
> e.g. CONFIG_IS_ENABLED(CLK) for CONFIG_CLK. Some of these were being
> fixed every now and then, see:
>
> commit 71ba2cb0d678 ("board: stm32mp1: correct CONFIG_IS_ENABLED usage for LED")
> commit a5ada25e4213 ("rockchip: clk: fix wrong CONFIG_IS_ENABLED handling")
> commit 5daf6e56d36c ("common: console: Fix duplicated CONFIG in silent env callback")
> commit 48bfc31b6484 ("MIPS: bootm: Fix broken boot_env_legacy codepath")
>
> Fix all files found by `git grep "CONFIG_IS_ENABLED(CONFIG"` by running
> ':%s/CONFIG_IS_ENABLED(CONFIG_\(\w+\))/CONFIG_IS_ENABLED(\1)/g' in vim.
>
> Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
> Reviewed-by: Simon Glass <sjg@chromium.org>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20201014/58ba4183/attachment.sig>
prev parent reply other threads:[~2020-10-14 17:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 6:57 [PATCH v2 1/2] treewide: Fix wrong CONFIG_IS_ENABLED() handling Alper Nebi Yasak
2020-10-05 6:57 ` [PATCH v2 2/2] checkpatch.pl: Make CONFIG_IS_ENABLED(CONFIG_*) an error Alper Nebi Yasak
2020-10-05 10:56 ` Simon Glass
2020-10-14 17:43 ` Tom Rini
2020-10-14 17:43 ` Tom Rini [this message]
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=20201014174324.GL14816@bill-the-cat \
--to=trini@konsulko.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 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.