From: John Bonesio <bones@bonesio.net>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: John Bonesio <bones@secretlab.ca>,
devicetree-discuss@lists.ozlabs.org, jdl@jdl.com,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
david@gibson.dropbear.id.au
Subject: Re: [PATCH 1/5] scripts: dtc: Merge in changes from the dtc repository
Date: Tue, 16 Nov 2010 22:29:55 -0800 [thread overview]
Message-ID: <4CE37663.2080806@bonesio.net> (raw)
In-Reply-To: <AANLkTinYZYR_QtS5-Nodpaf2MBBuaw06SW9pDCNQ9ov3@mail.gmail.com>
Arg!
I had this working. I'll look into it.
- John
On 11/16/2010 10:11 PM, Grant Likely wrote:
> On Tue, Nov 16, 2010 at 1:49 PM, John Bonesio <bones@secretlab.ca> wrote:
>> Pull in recent changes from the main dtc repository. These changes primarily
>> allow multiple device trees to be declared which are merged by dtc. This
>> feature allows us to include a basic dts file and then provide more information
>> for the specific system through the merging functionality.
>>
>> Signed-off-by: John Bonesio <bones@secretlab.ca>
>> ---
>>
>> 0 files changed, 0 insertions(+), 0 deletions(-)
> ??? Something isn't right in patch generation.
>
> Also:
>
> ~/hacking/linux-2.6$ xc-6xx make -j3
> GEN /home/grant/hacking/linux-2.6.build/6xx/Makefile
> HOSTCC scripts/kconfig/zconf.tab.o
> HOSTLD scripts/kconfig/conf
> scripts/kconfig/conf --silentoldconfig Kconfig
> #
> # configuration written to .config
> #
> GEN /home/grant/hacking/linux-2.6.build/6xx/Makefile
> CHK include/linux/version.h
> UPD include/linux/version.h
> HOSTCC scripts/dtc/checks.o
> In file included from /home/grant/hacking/linux-2.6/scripts/dtc/checks.c:21:
> /home/grant/hacking/linux-2.6/scripts/dtc/dtc.h:37: fatal error:
> util.h: No such file or directory
> compilation terminated.
> make[3]: *** [scripts/dtc/checks.o] Error 1
> make[2]: *** [scripts/dtc] Error 2
> make[1]: *** [scripts] Error 2
> make[1]: *** Waiting for unfinished jobs....
> make: *** [sub-make] Error 2
> (devicetree/test) ~/hacking/linux-2.6$
>
> Looks like the updated dtc is broken.
>
> g.
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
next prev parent reply other threads:[~2010-11-17 6:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 20:49 [PATCH 0/5] Series short description John Bonesio
2010-11-16 20:49 ` [PATCH 1/5] scripts: dtc: Merge in changes from the dtc repository John Bonesio
2010-11-17 4:59 ` Grant Likely
2010-11-17 15:47 ` Jon Loeliger
2010-11-18 3:41 ` David Gibson
2010-11-17 5:56 ` Kyle Moffett
2010-11-17 5:59 ` Grant Likely
2010-11-17 15:51 ` Jon Loeliger
2010-11-17 6:11 ` Grant Likely
2010-11-17 6:29 ` John Bonesio [this message]
2010-11-16 20:50 ` [PATCH 2/5] powerpc/5200: dts: rename nodes to prepare for refactoring dts files John Bonesio
2010-11-17 5:03 ` Grant Likely
2010-11-16 20:50 ` [PATCH 3/5] powerpc/5200: dts: remove unused properties John Bonesio
2010-11-17 5:05 ` Grant Likely
2010-11-16 20:50 ` [PATCH 4/5] powerpc/5200: dts: Remove incorrect combatible strings John Bonesio
2010-11-17 5:08 ` Grant Likely
2010-11-16 20:50 ` [PATCH 5/5] powerpc/5200: dts: refactor dts files John Bonesio
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=4CE37663.2080806@bonesio.net \
--to=bones@bonesio.net \
--cc=bones@secretlab.ca \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=jdl@jdl.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).