[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161016161945.GA1456@gmail.com>
Date: Sun, 16 Oct 2016 18:19:45 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
linux-arch@...r.kernel.org,
Peter Oberparleiter <oberpar@...ux.vnet.ibm.com>,
Arnd Bergmann <arnd@...db.de>,
Kees Cook <keescook@...omium.org>,
Michal Marek <mmarek@...e.com>, x86@...nel.org,
"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
Thomas Garnier <thgarnie@...gle.com>
Subject: Re: [PATCH] kconfig.h: remove config_enabled() macro
* Masahiro Yamada <yamada.masahiro@...ionext.com> wrote:
> The use of config_enabled() is ambiguous. For config options,
> IS_ENABLED(), IS_REACHABLE(), etc. will make intention clearer.
> Sometimes config_enabled() has been used for non-config options
> because it is useful to check whether the given symbol is defined
> or not.
>
> I have been tackling on deprecating config_enabled(), and now is the
> time to finish this work.
>
> Some new users have appeared for v4.9-rc1, but it is trivial to
> replace them:
>
> - arch/x86/mm/kaslr.c
> replace config_enabled() with IS_ENABLED() because
> CONFIG_X86_ESPFIX64 and CONFIG_EFI are boolean.
Acked-by: Ingo Molnar <mingo@...nel.org>
Thanks,
Ingo
Powered by blists - more mailing lists