From: Hollis Blanchard <hollisb@us.ibm.com>
To: Jerone Young <jyoung5@us.ibm.com>
Cc: kvm-ppc-devel@lists.sourceforge.net, kvm-devel@lists.sourceforge.net
Subject: Re: [kvm-ppc-devel] [PATCH 1 of 7] Add libfdt to KVM userspace
Date: Wed, 12 Mar 2008 21:25:59 -0500 [thread overview]
Message-ID: <1205375159.9736.11.camel@basalt> (raw)
In-Reply-To: <cb3ca3805e7735fffcf4.1205297440@thinkpad.austin.ibm.com>
On Tue, 2008-03-11 at 23:50 -0500, Jerone Young wrote:
> diff --git a/libfdt/Makefile b/libfdt/Makefile
> new file mode 100644
> --- /dev/null
> +++ b/libfdt/Makefile
> @@ -0,0 +1,19 @@
> +include ../config.mak
> +include ../user/config.mak
> +
> +LIBFDT_OBJS = fdt.o fdt_ro.o fdt_wip.o fdt_sw.o fdt_rw.o fdt_strerror.o
> +
> +LIBFDT_INCLUDES = fdt.h libfdt.h
> +LIBFDT_EXTRA = libfdt_internal.h
> +
> +LIBFDT_LIB = libfdt.a
> +
> +CFLAGS += -I .
> +
> +all: libfdt.a
> +
> +libfdt.a: $(LIBFDT_OBJS)
> + $(AR) rcs $@ $^
> +
> +clean:
> + rm -rf *.o *.a
> diff --git a/libfdt/Makefile.libfdt b/libfdt/Makefile.libfdt
> new file mode 100644
> --- /dev/null
> +++ b/libfdt/Makefile.libfdt
> @@ -0,0 +1,14 @@
> +# Makefile.libfdt
> +#
> +# This is not a complete Makefile of itself. Instead, it is designed to
> +# be easily embeddable into other systems of Makefiles.
> +#
> +LIBFDT_SRCS = fdt.c fdt_ro.c fdt_wip.c fdt_sw.c fdt_rw.c fdt_strerror.c
> +LIBFDT_INCLUDES = fdt.h libfdt.h
> +LIBFDT_EXTRA = libfdt_internal.h
> +LIBFDT_LIB = libfdt/libfdt.a
> +
> +LIBFDT_OBJS = $(LIBFDT_SRCS:%.c=%.o)
> +
> +$(LIBFDT_objdir)/$(LIBFDT_LIB): $(addprefix $(LIBFDT_objdir)/,$(LIBFDT_OBJS))
> +
Why are you duplicating Makefile.libfdt instead of including it?
--
Hollis Blanchard
IBM Linux Technology Center
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-03-13 2:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 4:50 [PATCH 0 of 7] PowerPC kvm-userspace patches Jerone Young
2008-03-12 4:50 ` [PATCH 1 of 7] Add libfdt to KVM userspace Jerone Young
2008-03-13 2:25 ` Hollis Blanchard [this message]
2008-03-12 4:50 ` [PATCH 2 of 7] Add libfdt support to qemu Jerone Young
2008-03-12 4:50 ` [PATCH 3 of 7] Create new load_uboot() & gunzip support to uboot loader in Qemu Jerone Young
2008-03-13 2:36 ` [kvm-ppc-devel] " Hollis Blanchard
2008-03-13 20:09 ` Jerone Young
2008-03-12 4:50 ` [PATCH 4 of 7] Add PPC 440EP bamboo board device tree source & binary into qemu Jerone Young
2008-03-13 2:42 ` [kvm-ppc-devel] " Hollis Blanchard
2008-03-13 20:24 ` Jerone Young
2008-03-12 4:50 ` [PATCH 5 of 7] Add dynamic device tree manipulation & change uboot loader for PPC bamboo board model Jerone Young
2008-03-13 2:53 ` [kvm-ppc-devel] " Hollis Blanchard
2008-03-13 22:27 ` Jerone Young
2008-03-12 4:50 ` [PATCH 6 of 7] Modify PPC bamboo & ppc440 board models Jerone Young
2008-03-12 4:50 ` [PATCH 7 of 7] Add ability to specify ram on command line for bamboo board model Jerone Young
2008-03-13 2:23 ` [kvm-ppc-devel] " Hollis Blanchard
2008-03-13 2:55 ` [kvm-ppc-devel] [PATCH 0 of 7] PowerPC kvm-userspace patches Hollis Blanchard
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=1205375159.9736.11.camel@basalt \
--to=hollisb@us.ibm.com \
--cc=jyoung5@us.ibm.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=kvm-ppc-devel@lists.sourceforge.net \
/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