From: Sam Ravnborg <sam@ravnborg.org>
To: Masahiro Yamada <yamada.m@jp.panasonic.com>
Cc: linux-kbuild@vger.kernel.org, Michal Marek <mmarek@suse.cz>
Subject: Re: [PATCH] kbuild: rename CONFIG_SHELL to KBUILD_SHELL
Date: Mon, 9 Jun 2014 20:15:26 +0200 [thread overview]
Message-ID: <20140609181526.GA1414@ravnborg.org> (raw)
In-Reply-To: <1402317082-21184-1-git-send-email-yamada.m@jp.panasonic.com>
On Mon, Jun 09, 2014 at 09:31:22PM +0900, Masahiro Yamada wrote:
> All the macros with CONFIG_ prefix are supposed to be defined
> in Kconfig. But CONFIG_SHELL is defined in the top Makefile,
> violating the namespace rule.
>
> Is is impossible to move CONFIG_SHELL definition to Kconfig.
> Configuration rules depend on "outputmakefile" rule where
> CONFIG_SHELL is already used.
> (Kbuild has to know which shell to use before invoking "make config".)
>
> So, it seems better to rename CONFIG_SHELL.
> Because "SHELL" is a special variable for GNU make, we should not
> use it. It looks like "KBUILD_SHELL" is a good choice.
>
> Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
> Cc: Sam Ravnborg <sam@ravnborg.org>
> Cc: Michal Marek <mmarek@suse.cz>
Acked-by: Sam Ravnborg <sam@ravnborg.org>
Please do a follow-up path that adds this variable to the list
in Documentation/kbuild/kbuild.txt
And please cc: the x86 people - thay have some patches that
uses CONFIG_SHELL IIRC.
The original (CONFIG_SHELL) was missing which is why you did not catch this.
Sam
next prev parent reply other threads:[~2014-06-09 18:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 12:31 [PATCH] kbuild: rename CONFIG_SHELL to KBUILD_SHELL Masahiro Yamada
2014-06-09 18:15 ` Sam Ravnborg [this message]
2014-06-09 20:50 ` Michal Marek
2014-06-09 21:18 ` Sam Ravnborg
2014-06-09 22:56 ` Michal Marek
2014-06-10 1:11 ` 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=20140609181526.GA1414@ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=yamada.m@jp.panasonic.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.