On Tue, 30 Oct 2012 16:24:05 -0600 Stephen Warren <swar...@wwwdotorg.org> wrote:
> On 10/30/2012 03:57 PM, Kim Phillips wrote: > > Projects such as linux and u-boot run sparse on libfdt. libfdt > > contains the notion of endianness via usage of endian conversion > > functions such as fdt32_to_cpu. As such, in order to pass endian > > checks, libfdt has to annotate its fdt variables as big endian. > > This patch does that ifdef __CHECKER__ (a symbol sparse defines), > > for two new fdt types: fdt32_t and fdt64_t, and subsequently > > silences warnings emitted by sparse when parsing libfdt. > > Should libfdt patches be committed to the main dtc repository (which I > assume is also upstream for libfdt?) rather than U-Boot first? that's what this is meant to be: a patch for dtc, cc: u-boot, since it was originally a patch to u-boot's copy. Fyi, dtc sumbission guidelines dictate To: jdl, Cc: devicetree-discuss... > Otherwise, if we want to bring in a new libfdt from upstream, that would > trash all the U-Boot-specific changes in U-Boot's copy of libfdt. right, this patch is for the dtc. I assume gvb will pull it into u-boot once it's applied. Kim _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot