public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 01/10] mkconfig: parse top level makefile target to multiple config targets
Date: Tue, 08 Sep 2009 15:58:21 -0500	[thread overview]
Message-ID: <4AA6C56D.6030402@freescale.com> (raw)
In-Reply-To: <20090908204825.BDB45832E8DE@gemini.denx.de>

Wolfgang Denk wrote:
>> Would this still be a big problem if the auto-generated defines were put
>> in their own namespace (such as the CONFIG_MK_* that you suggested)?
> 
> Probably not a big problem, and maybe not even a practical problem.
> But it is still ugly, and nothing I really like.

Well, yes -- the long term, less-ugly solution is kconfig.

> But as it seems that nobody else cares about this, and I don;t have
> any better ideas either, I guess I should not block this.

Thanks.

-Scott

  reply	other threads:[~2009-09-08 20:58 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-18  7:37 [U-Boot] [PATCH 00/10] add boot from NAND/eSDHC/eSPI support Mingkai Hu
2009-08-18  7:37 ` [U-Boot] [PATCH 01/10] mkconfig: parse top level makefile target to multiple config targets Mingkai Hu
2009-08-18  7:37   ` [U-Boot] [PATCH 02/10] NAND boot: change NAND loader's relocate SP to CONFIG param Mingkai Hu
2009-08-18  7:37     ` [U-Boot] [PATCH 03/10] Add L2SRAM Register's macro definition Mingkai Hu
2009-08-18  7:37       ` [U-Boot] [PATCH 04/10] 85xx: add boot from NAND/eSDHC/eSPI support Mingkai Hu
2009-08-18  7:37         ` [U-Boot] [PATCH 05/10] NAND boot: MPC8536DS support Mingkai Hu
2009-08-18  7:37           ` [U-Boot] [PATCH 06/10] On-chip ROM " Mingkai Hu
2009-08-18  7:37             ` [U-Boot] [PATCH 07/10] Add README.mpc8536ds Mingkai Hu
2009-08-18  7:37               ` [U-Boot] [PATCH 08/10] Make mmc init come before env_relocate Mingkai Hu
2009-08-18  7:37                 ` [U-Boot] [PATCH 09/10] Add support for save environment variable to MMC/SD card Mingkai Hu
2009-08-18  7:37                   ` [U-Boot] [PATCH 10/10] Get the address of env on the SDCard Mingkai Hu
2009-08-20 14:44       ` [U-Boot] [PATCH 03/10] Add L2SRAM Register's macro definition Kumar Gala
2009-08-20  0:45     ` [U-Boot] [PATCH 02/10] NAND boot: change NAND loader's relocate SP to CONFIG param Kim Phillips
2009-08-18 15:07   ` [U-Boot] [PATCH 01/10] mkconfig: parse top level makefile target to multiple config targets Kumar Gala
2009-08-21  7:18     ` Hu Mingkai-B21284
2009-09-04 19:42       ` Wolfgang Denk
2009-09-07  8:54         ` Hu Mingkai-B21284
2009-09-07 10:18           ` Wolfgang Denk
2009-09-07 10:24             ` Hu Mingkai-B21284
2009-09-07 10:59               ` Wolfgang Denk
2009-09-07 12:18                 ` Hu Mingkai-B21284
2009-09-07 12:38                   ` Wolfgang Denk
2009-09-08 15:38                     ` Scott Wood
2009-09-08 17:46                       ` Wolfgang Denk
2009-09-08 20:21                         ` Scott Wood
2009-09-08 20:48                           ` Wolfgang Denk
2009-09-08 20:58                             ` Scott Wood [this message]
2009-09-09 16:02                               ` [U-Boot] 答复: " Hu Mingkai-B21284
2009-09-15 20:53                                 ` 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=4AA6C56D.6030402@freescale.com \
    --to=scottwood@freescale.com \
    --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