Alexandru Gagniuc (mr.nuke.me(a)gmail.com) just uploaded a new patch set to gerrit, which you can find at http://review.coreboot.org/11292
-gerrit
commit 518920d6fa93ae0006ed039b7152550eb63af631
Author: Alexandru Gagniuc <mr.nuke.me(a)gmail.com>
Date: Thu Aug 20 14:44:48 2015 -0400
cbfstool/Makefile.inc: Specify output filename in fmd_parser rule
The fmd_parser.c rule called $(YACC), assuming that the output
filename is "y.tab.c". This isn't always the case as illustrated by
$ YACC=bison make
When the output file is specified, cbfstool compiles with the above,
and as a bonus, we kill two useless "cp" invocations.
Change-Id: I4e892773f380d99705a2b752bd88e964cf8553eb
Signed-off-by: Alexandru Gagniuc <mr.nuke.me(a)gmail.com>
---
util/cbfstool/Makefile | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/util/cbfstool/Makefile b/util/cbfstool/Makefile
index 65d5710..7e8142b 100644
--- a/util/cbfstool/Makefile
+++ b/util/cbfstool/Makefile
@@ -61,9 +61,7 @@ fmd_scanner.c: fmd_scanner.l
fmd_parser.h: fmd_parser.c
fmd_parser.c: fmd_parser.y
- $(YACC) $(YFLAGS) -d $<
- mv -f y.tab.c $*.c
- mv -f y.tab.h $*.h
+ $(YACC) $(YFLAGS) -o "$*.c" -d $<
.PHONY: clean
clean:
the following patch was just integrated into master:
commit 43213be11657669a3bd93eb81320558ef1183faf
Author: Alexandru Gagniuc <mr.nuke.me(a)gmail.com>
Date: Thu Aug 20 12:51:48 2015 -0400
mainboard: Get CHROMEOS/MAINBOARD_HAS_CHROMEOS right (again)
CHROMEOS is a user-visible bool. It must not be 'select'ed in Kconfig.
That's why we have MAINBOARD_HAS_CHROMEOS. This is the fifth time I
find this being used wrong.
Why is this confusing/so hard to get right?
Change-Id: Icb4629355c63508f5a044b46842524b3d203c2da
Signed-off-by: Alexandru Gagniuc <mr.nuke.me(a)gmail.com>
Reviewed-on: http://review.coreboot.org/11290
Reviewed-by: Paul Menzel <paulepanter(a)users.sourceforge.net>
Tested-by: build bot (Jenkins)
Reviewed-by: Aaron Durbin <adurbin(a)chromium.org>
Reviewed-by: Stefan Reinauer <stefan.reinauer(a)coreboot.org>
See http://review.coreboot.org/11290 for details.
-gerrit
the following patch was just integrated into master:
commit af473ede1f8ff5fc63609b914570aad21827b2e7
Author: Patrick Georgi <patrick(a)georgi-clan.de>
Date: Fri Jul 17 23:35:54 2015 +0200
crossgcc: Update gcc to 5.2.0
All compilers built, incl. x86_64-elf as multilib and riscv-elf.
Change-Id: Iafa61b1d2ffc9c737ab67a417c62417593b69372
Signed-off-by: Patrick Georgi <patrick(a)georgi-clan.de>
Reviewed-on: http://review.coreboot.org/10975
Tested-by: Raptor Engineering Automated Test Stand <noreply(a)raptorengineeringinc.com>
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer(a)coreboot.org>
See http://review.coreboot.org/10975 for details.
-gerrit
the following patch was just integrated into master:
commit f58746bd33f28bc7625e4fd6b166b6f977253c7d
Author: Nico Huber <nico.huber(a)secunet.com>
Date: Wed Aug 19 17:22:26 2015 +0200
libpayload: Fix default_memmove() implementation
If I wanted to fill the whole memory address space with one byte, I
wouldn't try it that subtle.
With size_t beeing unsigned the loop condition >= 0 was always true.
Change-Id: Idee6a4901f6697093c88bda354b5e43066c0d948
Signed-off-by: Nico Huber <nico.huber(a)secunet.com>
Reviewed-on: http://review.coreboot.org/11286
Reviewed-by: Stefan Reinauer <stefan.reinauer(a)coreboot.org>
Reviewed-by: Aaron Durbin <adurbin(a)chromium.org>
Tested-by: build bot (Jenkins)
See http://review.coreboot.org/11286 for details.
-gerrit