All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/5] treewide: include libfdt_env.h before fdt.h
Date: Wed, 16 Jan 2013 18:36:03 -0600	[thread overview]
Message-ID: <1358382963.18317.17@snotra> (raw)
In-Reply-To: <20130116175904.47ee25bd2596f28796698759@freescale.com> (from kim.phillips@freescale.com on Wed Jan 16 17:59:04 2013)

On 01/16/2013 05:59:04 PM, Kim Phillips wrote:
> and, if including libfdt.h which includes libfdt_env.h in
> the correct order, don't include fdt.h before libfdt.h.
> 
> this is needed to get the fdt type definitions set from
> the project environment before fdt.h uses them.
> 
> Signed-off-by: Kim Phillips <kim.phillips@freescale.com>
> Cc: Jerry Van Baren <gvb.uboot@gmail.com>

Maybe fdt.h should include libfdt_env.h?

Or just always use libfdt.h as the public header.

-Scott

  reply	other threads:[~2013-01-17  0:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-16 23:59 [U-Boot] [PATCH 1/5] treewide: include libfdt_env.h before fdt.h Kim Phillips
2013-01-17  0:36 ` Scott Wood [this message]
2013-01-17 17:54   ` Kim Phillips
2013-01-17 17:54     ` [U-Boot] " Kim Phillips
     [not found]     ` <20130117115456.71a38e3275230cdbb175bfe4-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2013-01-17 18:32       ` Jerry Van Baren
2013-01-17 18:32         ` Jerry Van Baren
     [not found]         ` <50F843CD.1030309-He//nVnquyzQT0dZR+AlfA@public.gmane.org>
2013-01-17 23:50           ` David Gibson
2013-01-17 23:50             ` David Gibson
     [not found]             ` <20130117235048.GF26321-W9XWwYn+TF0XU02nzanrWNbf9cGiqdzd@public.gmane.org>
2013-01-18 11:59               ` Gerald Van Baren
2013-01-18 11:59                 ` Gerald Van Baren
     [not found]                 ` <50F93932.60700-He//nVnquyzQT0dZR+AlfA@public.gmane.org>
2013-01-21  0:17                   ` David Gibson
2013-01-21  0:17                     ` David Gibson
2013-01-17 23:48       ` David Gibson
2013-01-17 23:48         ` David Gibson
2013-01-18 12:02 ` Jerry Van Baren

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=1358382963.18317.17@snotra \
    --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 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.