From: Sam Ravnborg <sam@ravnborg.org>
To: Michal Marek <mmarek@suse.cz>
Cc: Masahiro Yamada <yamada.m@jp.panasonic.com>,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] kbuild: rename CONFIG_SHELL to KBUILD_SHELL
Date: Mon, 9 Jun 2014 23:18:58 +0200 [thread overview]
Message-ID: <20140609211858.GA2025@ravnborg.org> (raw)
In-Reply-To: <53961E26.5080704@suse.cz>
On Mon, Jun 09, 2014 at 10:50:46PM +0200, Michal Marek wrote:
> Dne 9.6.2014 20:15, Sam Ravnborg napsal(a):
> > And please cc: the x86 people - thay have some patches that
> > uses CONFIG_SHELL IIRC.
>
> Do you remember which patches? Looking at
>
> git diff kbuild/kbuild linux-next -- arch/x86
>
> The only occurrence of CONFIG_SHELL is in the rule for make kvmconfig.
> Which is a conflict that is trivially solved.
Yep - these were the ones I had in mind.
Sam
next prev parent reply other threads:[~2014-06-09 21:19 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
2014-06-09 20:50 ` Michal Marek
2014-06-09 21:18 ` Sam Ravnborg [this message]
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=20140609211858.GA2025@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox