From: Michal Marek <mmarek@suse.cz>
To: Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Michal Simek <michal.simek@xilinx.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Nicolas Pitre <nicolas.pitre@linaro.org>,
linux-arch@vger.kernel.org
Subject: Re: [PATCH 5/5] vmlinux.lds.h: replace config_enabled() with IS_ENABLED()
Date: Mon, 20 Jun 2016 22:45:49 +0200 [thread overview]
Message-ID: <576855FD.6020202@suse.cz> (raw)
In-Reply-To: <1465883938-25194-5-git-send-email-yamada.masahiro@socionext.com>
Dne 14.6.2016 v 07:58 Masahiro Yamada napsal(a):
> The use of config_enabled() against config options is ambiguous.
>
> Now, IS_ENABLED() is implemented purely with macro expansion, so
> let's replace config_enabled() with IS_ENABLED().
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
I applied the whole series to kbuild.git#kbuild.
Michal
next prev parent reply other threads:[~2016-06-20 20:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 5:58 [PATCH 1/5] kconfig.h: use __is_defined() to check if MODULE is defined Masahiro Yamada
2016-06-14 5:58 ` [PATCH 2/5] export.h: use __is_defined() to check if __KSYM_* " Masahiro Yamada
2016-06-14 17:10 ` Nicolas Pitre
2016-06-14 5:58 ` [PATCH 3/5] kconfig.h: use already defined macros for IS_REACHABLE() define Masahiro Yamada
2016-06-14 5:58 ` [PATCH 4/5] kconfig.h: allow to use IS_{ENABLE,REACHABLE} in macro expansion Masahiro Yamada
2016-06-14 5:58 ` [PATCH 5/5] vmlinux.lds.h: replace config_enabled() with IS_ENABLED() Masahiro Yamada
2016-06-20 20:45 ` Michal Marek [this message]
2016-06-20 23:20 ` Masahiro Yamada
2016-06-21 9:25 ` Arnd Bergmann
2016-06-22 6:52 ` Masahiro Yamada
2016-06-23 8:07 ` Masahiro Yamada
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=576855FD.6020202@suse.cz \
--to=mmarek@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=nicolas.pitre@linaro.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@linux-foundation.org \
--cc=yamada.masahiro@socionext.com \
/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.