All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] RFC common omap3 subconfig ? was Re: [PATCH] OMAP3EVM: Increase bootargs string length.
Date: Fri, 18 Dec 2009 09:43:35 +0100	[thread overview]
Message-ID: <200912180943.35145.sr@denx.de> (raw)
In-Reply-To: <4B2A773E.2010609@denx.de>

Hi Heiko,

On Thursday 17 December 2009 19:23:58 Heiko Schocher wrote:
> > We already have some similar common config files. Take a look for example
> > at the AMCC config header:
> >
> > include/configs/amcc-common.h
> 
> I vote for collecting "common config files" in a subdir:
> 
> include/configs/common
> 
> for example:
> include/configs/common/mpc83xx.h
> 
> collects all common config options for 83xx boards.
> and so on for all other architectures/manufacturer ...
> 
> And a "#include "configs/common/..." provides enough
> information, what will come in with that include ...

Yes, such a directory could make sense. But please note that we already have 
something similar:

include/asm-ppc/config.h

The other architectures have this file as well, but most of them don't define 
much in it. Not sure how to best merge/consolidate this.

Cheers,
Stefan

--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de

      reply	other threads:[~2009-12-18  8:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-17 13:29 [U-Boot] [PATCH] OMAP3EVM: Increase bootargs string length Sriramakrishnan
2009-12-17 14:26 ` Dirk Behme
2009-12-17 14:48   ` Govindarajan, Sriramakrishnan
2009-12-17 15:55   ` [U-Boot] RFC common omap3 subconfig ? was " Tom
2009-12-17 15:58     ` Premi, Sanjeev
2009-12-17 16:07       ` Dirk Behme
2009-12-17 16:36         ` Stefan Roese
2009-12-17 18:23           ` Heiko Schocher
2009-12-18  8:43             ` Stefan Roese [this message]

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=200912180943.35145.sr@denx.de \
    --to=sr@denx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.