From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] Add an architecture specific config.h for common defines
Date: Fri, 6 Feb 2009 07:38:01 +0100 [thread overview]
Message-ID: <20090206063801.GI4580@game.jcrosoft.org> (raw)
In-Reply-To: <1233888058-21503-1-git-send-email-galak@kernel.crashing.org>
On 20:40 Thu 05 Feb , Kumar Gala wrote:
> We have common defines that we duplicate in various ways. Having an
> arch specific config.h gives us a common location for those defines.
>
> Eventually we should be able to relace this when we have proper Kconfig
> support.
>
I've already propose this to Wolfgang when handling FIT and FDT problem and he
NACK it
Best Regards,
J.
next prev parent reply other threads:[~2009-02-06 6:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 2:40 [U-Boot] [PATCH 1/2] Add an architecture specific config.h for common defines Kumar Gala
2009-02-06 2:40 ` [U-Boot] [PATCH 2/2] ppc: Move CONFIG_MAX_MEM_MAPPED to common config.h Kumar Gala
2009-02-09 15:28 ` Stefan Roese
2009-02-09 23:44 ` Wolfgang Denk
2009-02-06 6:38 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2009-02-09 23:44 ` [U-Boot] [PATCH 1/2] Add an architecture specific config.h for common defines 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=20090206063801.GI4580@game.jcrosoft.org \
--to=plagnioj@jcrosoft.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