From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] [BUILD] conditionally compile libfdt/*.c in libfdt/Makefile
Date: Wed, 21 Nov 2007 10:15:24 -0500 [thread overview]
Message-ID: <47444B8C.7010503@ge.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0711210849570.12880@blarg.am.freescale.net>
Kumar Gala wrote:
> Modify libfdt/Makefile to conditionally compile the *.c files based
> on the board config.
>
> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
> ---
>
> This is against u-boot-testing
>
> libfdt/Makefile | 2 +-
> libfdt/fdt.c | 5 -----
> libfdt/fdt_ro.c | 5 -----
> libfdt/fdt_rw.c | 5 -----
> libfdt/fdt_strerror.c | 5 -----
> libfdt/fdt_sw.c | 5 -----
> libfdt/fdt_wip.c | 5 -----
> 7 files changed, 1 insertions(+), 31 deletions(-)
Joy!
It looks like the side effect of Grant's improvement just removed all of
the #ifdefs I hacked into the libfdt primary .c files.
Side note: I was playing last night with the "what if" of deleting (git
rm libfdt/*.[ch]) all the "standard" libfdt code, then re-importing it.
Effectively rebaselining in a kerchunk rather than a patch-forward
that Kumar has been doing.
The advantages would be:
* It would be clearer that u-boot/libfdt version 2007-11-X == dtc/libfdt
version 2007-11-X and then we could more easily track changes forward.
* The removal patch is less than 40K (email list limit), but the
re-import patch is around 70K (IIRC) so that doesn't help.
My current conclusion is that it isn't worth the effort.
* The re-import still has a size vs. email list problem
* Since some libfdt routines changed, other (client) routines must be
changed at the same time as the re-import (Kumar's patch rolls libfdt
forward _and_ fixes the handful of calls, so it doesn't have a "broken
spot" in between patches).
Thanks to all!
gvb
next prev parent reply other threads:[~2007-11-21 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 14:50 [U-Boot-Users] [PATCH] [BUILD] conditionally compile libfdt/*.c in libfdt/Makefile Kumar Gala
2007-11-21 15:15 ` Jerry Van Baren [this message]
2007-11-21 15:29 ` Kumar Gala
2007-11-21 16:42 ` Jon Loeliger
2007-11-21 16:41 ` Jon Loeliger
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=47444B8C.7010503@ge.com \
--to=gerald.vanbaren@ge.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.