From: "Timur Tabi" <timur@freescale.com>
To: linuxppc-dev@ozlabs.org, benh@kernel.crashing.org
Subject: Re: [PATCH] powerpc: remove CHRP and PMAC support from defconfigs, fix Kconfigs
Date: Wed, 8 Oct 2008 10:28:53 -0500 [thread overview]
Message-ID: <ed82fe3e0810080828r115b3e85laf08e8d1e47faf42@mail.gmail.com> (raw)
In-Reply-To: <1222449586-14622-1-git-send-email-timur@freescale.com>
On Fri, Sep 26, 2008 at 12:19 PM, Timur Tabi <timur@freescale.com> wrote:
> The Kconfig files for PowerPC CHRP and PMAC support had "default=y" for some
> Kconfig options, and this caused support for CHRP and PMAC platforms to be
> enabled incorrectly for several platforms. Fix the Kconfigs and the
> affected defconfigs.
Ben,
When you applied this patch, you removed the Kconfig changes. Without
those, doing a "make xxx_defconfig" will just add "CONFIG_PPC_PMAC=y"
and "CONFIG_PPC_CHRP=y" to the .config!
$ make 83xx/mpc834x_itxgp_defconfig
HOSTCC scripts/basic/fixdep
HOSTCC scripts/basic/docproc
HOSTCC scripts/kconfig/conf.o
HOSTCC scripts/kconfig/kxgettext.o
SHIPPED scripts/kconfig/zconf.tab.c
SHIPPED scripts/kconfig/lex.zconf.c
SHIPPED scripts/kconfig/zconf.hash.c
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
#
# configuration written to .config
#
$ grep CHRP .config
CONFIG_PPC_CHRP=y
So please apply my *original* patch.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-10-08 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 17:19 [PATCH] powerpc: remove CHRP and PMAC support from defconfigs, fix Kconfigs Timur Tabi
2008-10-06 21:52 ` Timur Tabi
2008-10-08 15:28 ` Timur Tabi [this message]
2008-10-08 19:19 ` Benjamin Herrenschmidt
2008-10-08 19:22 ` Timur Tabi
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=ed82fe3e0810080828r115b3e85laf08e8d1e47faf42@mail.gmail.com \
--to=timur@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).