From: David Gibson <david@gibson.dropbear.id.au>
To: Kim Phillips <kim.phillips@freescale.com>
Cc: u-boot@lists.denx.de, jdl@jdl.com, devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH v4 3/4] dtc/libfdt: introduce fdt types for annotation by endian checkers
Date: Mon, 3 Dec 2012 15:05:34 +1100 [thread overview]
Message-ID: <20121203040534.GD4293@truffula.fritz.box> (raw)
In-Reply-To: <20121128173301.2b52b22a39fe6c3ce5a088fb@freescale.com>
On Wed, Nov 28, 2012 at 05:33:01PM -0600, 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 such that sparse
> can warn when mixing bitwise and regular integers. This patch adds
> these new fdtXX_t types and, ifdef __CHECKER__ (a symbol sparse
> defines), includes the bitwise annotation.
>
> Signed-off-by: Kim Phillips <kim.phillips@freescale.com>
Much better, thanks
Acked-by: David Gibson <david@gibson.dropbear.id.au>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2012-12-03 4:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1350433728-24120-1-git-send-email-kim.phillips@freescale.com>
[not found] ` <507F4B0B.1020401@gmail.com>
[not found] ` <20121018121112.GI23523@truffula.fritz.box>
[not found] ` <20121018173022.32f1745249d162d1aa453694@freescale.com>
[not found] ` <20121019004324.GN23523@truffula.fritz.box>
2012-10-30 21:57 ` [PATCH] libfdt: introduce fdt type annotation for use by endian checkers Kim Phillips
2012-10-30 22:24 ` Stephen Warren
2012-10-30 22:27 ` Kim Phillips
[not found] ` <20121030165754.65b34c78cd0d3a0d6ab7d34e-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2012-11-06 7:48 ` David Gibson
2012-11-14 0:34 ` [PATCH 3/4 v2] dtc/libfdt: introduce fdt types for annotation " Kim Phillips
[not found] ` <20121113183417.7706e5c6044eb273309ef46e-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2012-11-14 14:42 ` Jon Loeliger
2012-11-15 0:59 ` [PATCH v2 1/4] dtc/tests: don't include fdt.h prior to libfdt.h Kim Phillips
[not found] ` <1352941199-19393-1-git-send-email-kim.phillips-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2012-11-15 0:59 ` [PATCH v2 2/4] dtc/fdtdump: include libfdt_env.h prior to fdt.h Kim Phillips
2012-11-15 0:59 ` [PATCH v3 3/4] dtc/libfdt: introduce fdt types for annotation by endian checkers Kim Phillips
[not found] ` <1352941199-19393-3-git-send-email-kim.phillips-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2012-11-15 4:43 ` David Gibson
2012-11-15 5:12 ` Kim Phillips
[not found] ` <20121114231204.8f19082c7acc1cea2a2d794f-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2012-11-19 2:30 ` David Gibson
2012-11-28 23:33 ` [PATCH v4 " Kim Phillips
2012-12-03 4:05 ` David Gibson [this message]
[not found] ` <20121128173301.2b52b22a39fe6c3ce5a088fb-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2013-01-06 21:52 ` Jon Loeliger
2012-11-15 0:59 ` [PATCH v2 4/4] dtc/libfdt: uintXX_t to fdtXX_t conversion Kim Phillips
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=20121203040534.GD4293@truffula.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=jdl@jdl.com \
--cc=kim.phillips@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).