devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Gerald Van Baren <vanbaren-He//nVnquyzQT0dZR+AlfA@public.gmane.org>
Cc: Devicetree Discuss
	<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: Re: [PATCH] Use the libfdt.h include as the interface definition
Date: Tue, 29 Jan 2013 12:20:57 +1100	[thread overview]
Message-ID: <20130129012057.GD16729@truffula.fritz.box> (raw)
In-Reply-To: <5105E3EA.2070306-He//nVnquyzQT0dZR+AlfA@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 1986 bytes --]

On Sun, Jan 27, 2013 at 09:35:22PM -0500, Gerald Van Baren wrote:
> libfdt.h is the libfdt interface definition.  It includes fdt.h and
> libfdt_env.h, so there is no reason to include those in the general code.
> 
> Signed-off-by: Gerald Van Baren <vanbaren-He//nVnquyzQT0dZR+AlfA@public.gmane.org>
> ---
> 
> No code changes, just cleaning up the #include situation WRT libfdt.h,
> fdt.h, and libfdt_env.h (the later two being redundant).
> 
> I looked at moving the fdt64_t, fdt32_t, fdt16_t definitions from
> libfdt_env.h to fdt.h.  I'm not sure this is a Good Thing[tm], but will
> send a separate patch for consideration and discussion.
> 
>  dtc.h                    |    3 +--
>  fdtdump.c                |    3 +--
>  libfdt/fdt.c             |    3 ---
>  libfdt/fdt_empty_tree.c  |    3 ---
>  libfdt/fdt_ro.c          |    3 ---
>  libfdt/fdt_rw.c          |    3 ---
>  libfdt/fdt_strerror.c    |    3 ---
>  libfdt/fdt_sw.c          |    3 ---
>  libfdt/fdt_wip.c         |    3 ---
>  libfdt/libfdt_internal.h |    1 -
>  10 files changed, 2 insertions(+), 26 deletions(-)
> 
> diff --git a/dtc.h b/dtc.h
> index 3e42a07..a032645 100644
> --- a/dtc.h
> +++ b/dtc.h
> @@ -32,8 +32,7 @@
>  #include <errno.h>
>  #include <unistd.h>
> 
> -#include <libfdt_env.h>
> -#include <fdt.h>
> +#include <libfdt.h>

For dtc.h, this is wrong - dtc uses the structures in fdt.h, but
(deliberately) nothing in libfdt.h.

For the other cases, I'm a bit undecided.  As you say, the individual
includes are redundant.  In some cases the explicit inclusions kind of
document that the C code has direct dependencies on the stuff in
libfdt_env.h and fdt.h as well as the indirect dependencies from the
libfdt.h API.  I'm not really sold either way.

-- 
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

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 192 bytes --]

_______________________________________________
devicetree-discuss mailing list
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
https://lists.ozlabs.org/listinfo/devicetree-discuss

      parent reply	other threads:[~2013-01-29  1:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-28  2:35 [PATCH] Use the libfdt.h include as the interface definition Gerald Van Baren
     [not found] ` <5105E3EA.2070306-He//nVnquyzQT0dZR+AlfA@public.gmane.org>
2013-01-29  1:20   ` David Gibson [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=20130129012057.GD16729@truffula.fritz.box \
    --to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=vanbaren-He//nVnquyzQT0dZR+AlfA@public.gmane.org \
    /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).