From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/2] mkconfig: split the board make target to multiple config targets
Date: Mon, 14 Sep 2009 14:47:47 +0200 [thread overview]
Message-ID: <4AAE3B73.5030400@monstr.eu> (raw)
In-Reply-To: <20090911080746.5CAA4832E8DE@gemini.denx.de>
Wolfgang Denk wrote:
> Dear Mingkai Hu,
>
> In message <1252466603-25103-1-git-send-email-Mingkai.hu@freescale.com> you wrote:
>> To simplify the top level makefile it useful to be able to parse
>> the top level makefile target to multiple individual target, then
>> put them to the config.h, leave the board config file to handle
>> the different targets.
>>
>> Note that this method uses the '_'(underline) as the delimiter when
>> splits the board make target.
>>
>> Signed-off-by: Mingkai Hu <Mingkai.hu@freescale.com>
>> ---
>>
>> According to the comments from Wolfgang and Scott, I modified
>> the patch and made some modification over v1:
>>
>> - remove the sectence thats puts the splited variables to the
>> config.mk, we can use the CONFIG_MK_* in the board config file
>> to override the variable in the board config file.
>>
>> - change CONFIG_OPT_* to CONFIG_MK_*
>>
>> mkconfig | 7 +++++++
>> 1 files changed, 7 insertions(+), 0 deletions(-)
>
> Arghhh... It seems this patch has not been well tested. Obviously
> never ever ran a MAKEALL over all PPC boards. It causes tons of
> messages like that:
>
> include/config.h:2:25: warning: missing whitespace after the macro name
>
> This patch breaks building for a number of boards / configurations,
> especially:
>
> xilinx-ppc405-generic_flash
> xilinx-ppc405-generic
> xilinx-ppc440-generic_flash
> xilinx-ppc440-generic
> VoVPN-GW_66MHz
> VoVPN-GW_100MHz
> EB+MCF-EV123
> EB+MCF-EV123_internal
> microblaze-generic
I can confirm problem on Microblaze.
Please revert that patches.
Thanks,
Michal
> favr-32-ezkit
>
>
> Shall I revert that patch?
>
> Best regards,
>
> Wolfgang Denk
>
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
next prev parent reply other threads:[~2009-09-14 12:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 3:23 [U-Boot] [PATCH v2 1/2] mkconfig: split the board make target to multiple config targets Mingkai Hu
2009-09-09 3:23 ` [U-Boot] [PATCH 2/2] mpc8536: simplify the top makefile for 36-bit config Mingkai Hu
2009-09-11 8:07 ` [U-Boot] [PATCH v2 1/2] mkconfig: split the board make target to multiple config targets Wolfgang Denk
2009-09-11 8:12 ` Stefan Roese
2009-09-11 8:25 ` Wolfgang Denk
2009-09-11 8:46 ` Hu Mingkai-B21284
2009-09-11 15:20 ` Scott Wood
2009-09-11 15:35 ` Kumar Gala
2009-09-11 18:09 ` Wolfgang Denk
2009-09-14 2:44 ` Hu Mingkai-B21284
2009-09-14 12:47 ` Michal Simek [this message]
2009-09-15 20:20 ` Wolfgang Denk
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=4AAE3B73.5030400@monstr.eu \
--to=monstr@monstr.eu \
--cc=u-boot@lists.denx.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