public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] Move and rename common headers from under board/davinci
Date: Fri, 22 Oct 2010 11:47:16 +0200	[thread overview]
Message-ID: <20101022094716.EEF45136320@gemini.denx.de> (raw)
In-Reply-To: <20101022084641.GD8597@Hardy>

Dear Sughosh Ganu,

In message <20101022084641.GD8597@Hardy> you wrote:
>
> > Please don't. Assume that all config.mk files are candidates for
> > removal.
> > 
> > Rather put commonly used header files in places where they can be
> > found easily.
> 
>   Which is what i was trying in the first place :). Any place other
>   than the include directory would need us to specifiy the path to the
>   files. Where can we put such information then, if not
>   config.mk. Please let me know.

If you have common code and local header files that are only needed by
that code you should place this into the
arch/arm/cpu/arm926ejs/davinci/ directory, and use the #include "..."
notation.

Headers that are architecture specific, but otherwise global for all
boards, should probably go to arch/arm/include/asm/arch-davinci/, in
which case you can use #include <asm/arch/...>

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
On a clear disk you can seek forever.

      reply	other threads:[~2010-10-22  9:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-21 19:42 [U-Boot] [PATCH 1/2] Move and rename common headers from under board/davinci Sughosh Ganu
2010-10-21 20:30 ` Wolfgang Denk
2010-10-22  7:26   ` Sughosh Ganu
2010-10-22  7:56     ` Wolfgang Denk
2010-10-22  8:04       ` Sughosh Ganu
2010-10-22  8:26         ` Wolfgang Denk
2010-10-22  8:46           ` Sughosh Ganu
2010-10-22  9:47             ` Wolfgang Denk [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=20101022094716.EEF45136320@gemini.denx.de \
    --to=wd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox