From: Paul Cercueil <paul@crapouillou.net>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Arnd Bergmann <arnd@kernel.org>,
od@zcrc.me, Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] if_enabled.h: Add IF_ENABLED_OR_ELSE() and\r
IF_ENABLED() macros
Date: Wed, 09 Dec 2020 11:31:41 +0000 [thread overview]
Message-ID: <TCL2LQ.PG7DIQPDDGUT1@crapouillou.net> (raw)
In-Reply-To: <CACRpkdZFy8bvsV+HkzWsu0OKjg6i82o-mL+7v3_Ev5h_QR=xiA@mail.gmail.com>
Hi Linus,
Le mer. 9 déc. 2020 à 9:59, Linus Walleij <linus.walleij@linaro.org>
a écrit :
> On Tue, Dec 8, 2020 at 5:48 PM Paul Cercueil <paul@crapouillou.net>
> wrote:
>
>> Introduce a new header <linux/if_enabled.h>, that brings two new
>> macros:
>> IF_ENABLED_OR_ELSE() and IF_ENABLED().
>
> I understand what the patch is trying to do, but when we already have
> IS_ENABLED() in <linux/kconfig.h> this syntax becomes a big cognitive
> confusion for the mind.
>
> At least the commit needs to explain why it doesn't work to use
> IS_ENABLED() instead so that this is needed.
You can use IS_ENABLED(). Then you'd write:
field = IS_ENABLED(CONFIG_FOO) ? &my_ptr : NULL,
the IF_ENABLED() macro makes it a bit cleaner by allowing you to write:
field = IF_ENABLED(CONFIG_FOO, &my_ptr),
Cheers,
-Paul
> Certainly the build failures must be possible to solve so that this
> can live with the sibling IS_ENABLED() inside <linux/kconfig.h>,
> it can't be too hard.
>
> Yours,
> Linus Walleij
next prev parent reply other threads:[~2020-12-09 11:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 16:48 [PATCH 1/2] if_enabled.h: Add IF_ENABLED_OR_ELSE() and IF_ENABLED() macros Paul Cercueil
2020-12-08 16:48 ` [PATCH 2/2] pinctrl: ingenic: Only support SoCs enabled in config Paul Cercueil
2020-12-09 10:13 ` Daniel Palmer
2020-12-09 11:04 ` Arnd Bergmann
2020-12-08 17:39 ` [PATCH 1/2] if_enabled.h: Add IF_ENABLED_OR_ELSE() and IF_ENABLED() macros Randy Dunlap
2020-12-08 19:00 ` Paul Cercueil
2020-12-09 8:59 ` Linus Walleij
2020-12-09 11:31 ` Paul Cercueil [this message]
2020-12-09 9:38 ` Ard Biesheuvel
2020-12-09 11:27 ` Paul Cercueil
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=TCL2LQ.PG7DIQPDDGUT1@crapouillou.net \
--to=paul@crapouillou.net \
--cc=arnd@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=od@zcrc.me \
/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;
as well as URLs for NNTP newsgroup(s).