From: David Gibson <david@gibson.dropbear.id.au>
To: Jon Loeliger <jdl@jdl.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: DTC Updates
Date: Wed, 17 Oct 2007 10:34:56 +1000 [thread overview]
Message-ID: <20071017003456.GB28260@localhost.localdomain> (raw)
In-Reply-To: <E1IhmXN-0003CC-39@jdl.com>
On Tue, Oct 16, 2007 at 08:32:45AM -0500, Jon Loeliger wrote:
>
> Guys and Dolls,
>
> I pushed out all of David's recent DTC and libfdt patches.
> I also jammed the following patch into the mix as well.
>
> HTH,
> jdl
>
>
>
> commit 9e32930ebcacfcf7cb7c1c2b8e776eb3957cf6cb
> Author: Jon Loeliger <jdl@freescale.com>
> Date: Tue Oct 16 07:35:38 2007 -0500
>
> Restore warning message about bison expected output.
Heh, the removal was kind of deliberate, since I didn't think it was
actually all that much use. But I don't really care much one way or
the other.
I really wish bison would suppress these warnings in glr-parser mode.
>
> It was dropped in ad9593f229362782b953da4b805df713e8468df0.
>
> Signed-off-by: Jon Loeliger <jdl@jdl.com>
>
> diff --git a/Makefile b/Makefile
> index 84f0efe..d7d1af5 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -207,6 +207,7 @@ clean: libfdt_clean tests_clean
>
> %.tab.c %.tab.h %.output: %.y
> @$(VECHO) BISON $@
> + @$(VECHO) ---- Expect 2 s/r and 2 r/r. ----
> $(BISON) -d $<
>
> FORCE:
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>
--
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
prev parent reply other threads:[~2007-10-17 0:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 13:32 DTC Updates Jon Loeliger
2007-10-17 0:34 ` 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=20071017003456.GB28260@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=jdl@jdl.com \
--cc=linuxppc-dev@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).