From: Michal Simek <monstr@monstr.eu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kconfig: Use macros which are already defined
Date: Mon, 23 Feb 2015 11:23:14 +0100 [thread overview]
Message-ID: <54EAFF92.5070709@monstr.eu> (raw)
In-Reply-To: <fa1a28d64cb484535e355f364b49f5ab42b98f46.1418288403.git.michal.simek@xilinx.com>
[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]
Hi Andrew,
On 12/11/2014 10:00 AM, Michal Simek wrote:
> It is better to use macros which are already available
> because then there is just one location which needs to be change.
>
> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
> ---
>
> FYI: Fengguang's testing system doesn't show any build error.
> ---
> include/linux/kconfig.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/kconfig.h b/include/linux/kconfig.h
> index be342b94c640..71acdf650e2e 100644
> --- a/include/linux/kconfig.h
> +++ b/include/linux/kconfig.h
> @@ -28,7 +28,7 @@
> *
> */
> #define IS_ENABLED(option) \
> - (config_enabled(option) || config_enabled(option##_MODULE))
> + (IS_BUILTIN(option) || IS_MODULE(option))
>
> /*
> * IS_BUILTIN(CONFIG_FOO) evaluates to 1 if CONFIG_FOO is set to 'y', 0
> --
> 1.8.2.3
>
Can you please add this to your queue?
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-02-23 10:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 9:00 [PATCH] kconfig: Use macros which are already defined Michal Simek
2015-02-23 10:23 ` Michal Simek [this message]
2015-02-26 21:23 ` Andrew Morton
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=54EAFF92.5070709@monstr.eu \
--to=monstr@monstr.eu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
/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