From: Heiko Schocher <hs@denx.de>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/2] powerpc, mpc5200: update defconfig to fit with 2.6.37-rc4
Date: Mon, 13 Dec 2010 08:09:03 +0100 [thread overview]
Message-ID: <4D05C68F.4030600@denx.de> (raw)
In-Reply-To: <20101212084707.GA14580@pengutronix.de>
Hello Wolfram,
Wolfram Sang wrote:
> On Sat, Dec 11, 2010 at 07:13:00AM +0100, Heiko Schocher wrote:
>> Signed-off-by: Heiko Schocher <hs@denx.de>
>
> I'd say the two patches can be merged. Dunno what Grant prefers whom you should
> CC as he is the maintainer.
I prefer the split in two patches, so we can see, what is added
by the charon board, and what by "make mpc5200_defconfig" ...
>> cc: Wolfram Sang <w.sang@pengutronix.de>
>> cc: linuxppc-dev@lists.ozlabs.org
>> ---
>> - based against 2.6.37-rc4
>> - I did the following steps to generate this patch:
>>
>> make mpc5200_defconfig
>> make savedefconfig
>> cp ./defconfig arch/powerpc/configs/mpc5200_defconfig
>>
>> arch/powerpc/configs/mpc5200_defconfig | 5 +----
>> 1 files changed, 1 insertions(+), 4 deletions(-)
>>
>> diff --git a/arch/powerpc/configs/mpc5200_defconfig b/arch/powerpc/configs/mpc5200_defconfig
>> index 7376e27..6f75623 100644
>> --- a/arch/powerpc/configs/mpc5200_defconfig
>> +++ b/arch/powerpc/configs/mpc5200_defconfig
>> @@ -1,5 +1,6 @@
>> CONFIG_EXPERIMENTAL=y
>> CONFIG_SYSVIPC=y
>> +CONFIG_SPARSE_IRQ=y
>> CONFIG_LOG_BUF_SHIFT=14
>> CONFIG_BLK_DEV_INITRD=y
>> # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
>> @@ -20,7 +21,6 @@ CONFIG_PPC_BESTCOMM=y
>> CONFIG_SIMPLE_GPIO=y
>> CONFIG_NO_HZ=y
>> CONFIG_HIGH_RES_TIMERS=y
>> -CONFIG_SPARSE_IRQ=y
>> CONFIG_PM=y
>> CONFIG_NET=y
>> CONFIG_PACKET=y
>> @@ -52,7 +52,6 @@ CONFIG_PROC_DEVICETREE=y
>> CONFIG_BLK_DEV_LOOP=y
>> CONFIG_BLK_DEV_RAM=y
>> CONFIG_BLK_DEV_RAM_SIZE=32768
>> -CONFIG_EEPROM_AT24=y
>
> NACK.
... I did just the steps above mentioned, so this is
automagically done by "make mpc5200_defconfig" !
>> CONFIG_SCSI_TGT=y
>> CONFIG_BLK_DEV_SD=y
>> CONFIG_CHR_DEV_SG=y
>> @@ -114,7 +113,6 @@ CONFIG_RTC_DRV_DS1307=y
>> CONFIG_EXT2_FS=y
>> CONFIG_EXT3_FS=y
>> # CONFIG_EXT3_DEFAULTS_TO_ORDERED is not set
>> -CONFIG_INOTIFY=y
>
> Are you sure?
See comment above, did just the "make mpc5200_defconfig"
step ...
>> CONFIG_MSDOS_FS=y
>> CONFIG_VFAT_FS=y
>> CONFIG_PROC_KCORE=y
>> @@ -132,5 +130,4 @@ CONFIG_PRINTK_TIME=y
>> CONFIG_DEBUG_KERNEL=y
>> CONFIG_DETECT_HUNG_TASK=y
>> CONFIG_DEBUG_INFO=y
>> -# CONFIG_RCU_CPU_STALL_DETECTOR is not set
>> # CONFIG_CRYPTO_ANSI_CPRNG is not set
>> --
>> 1.7.2.3
Thanks for the review!
bye,
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2010-12-13 7:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-11 6:13 [PATCH 1/2] powerpc, mpc5200: update defconfig to fit with 2.6.37-rc4 Heiko Schocher
2010-12-11 6:13 ` [PATCH 2/2] powerpc, mpc5200: update mpc5200_defconfig to fit for charon board Heiko Schocher
2010-12-12 8:47 ` [PATCH 1/2] powerpc, mpc5200: update defconfig to fit with 2.6.37-rc4 Wolfram Sang
2010-12-13 7:09 ` Heiko Schocher [this message]
2010-12-13 10:06 ` Wolfram Sang
2010-12-13 10:12 ` Heiko Schocher
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=4D05C68F.4030600@denx.de \
--to=hs@denx.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=w.sang@pengutronix.de \
/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).