On Mon, Dec 4, 2017 at 5:33 PM, Tom Rini trini@konsulko.com wrote:

Hey all,

So it's release day and I've put up v2018.01-rc1. The merge window is now closed and I've updated git and the tarballs are also up now.

I think my patch queue is in OK shape currently, but I need to pick up a few series once I've had a chance to test them more, and I expect a new EFI PR to come along soon too. Once again, I'm going to otherwise try and be pretty strict about what goes in, and more so as time goes on. I will follow the usual rule of an -rc every other Monday

Are things that were already submitted to the mailing list before the RC1 still open for being accepted into the 2018.01 release or will they be held until 2018.03?

and we're looking at release on Jan 8th, 2018.

Happy New Year. :-)

Thanks all!

Thanks for all that you do.

-- Tom

---

U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot

Hi Tom,

So it's release day and I've put up v2018.01-rc1. The merge window is now closed and I've updated git and the tarballs are also up now.

I think my patch queue is in OK shape currently, but I need to pick up a few series once I've had a chance to test them more, and I expect a new EFI PR to come along soon too. Once again, I'm going to otherwise try and be pretty strict about what goes in, and more so as time goes on. I will follow the usual rule of an -rc every other Monday and we're looking at release on Jan 8th, 2018.

I'm seeing some failures when just building the various utils with defconfig on Fedora 28 (gcc 7.2.1) on any architecture.

Peter

make -C /builddir/build/BUILD/u-boot-2018.01-rc1/builds KBUILD_SRC=/builddir/build/BUILD/u-boot-2018.01-rc1 \ -f /builddir/build/BUILD/u-boot-2018.01-rc1/Makefile defconfig make[1]: Entering directory '/builddir/build/BUILD/u-boot-2018.01-rc1/builds' make -f ../scripts/Makefile.build obj=scripts/basic ln -fsn .. source /bin/sh ../scripts/mkmakefile \ .. . 2018 01 GEN ./Makefile gcc -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -Wp,-MD,scripts/basic/.fixdep.d -Iscripts/basic -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o scripts/basic/fixdep ../scripts/basic/fixdep.c rm -f .tmp_quiet_recordmcount make -f ../scripts/Makefile.build obj=scripts/kconfig defconfig gcc -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -Wp,-MD,scripts/kconfig/.conf.o.d -Iscripts/kconfig -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -DCURSES_LOC="<curses.h>" -DLOCALE -DKBUILD_NO_NLS -c -o scripts/kconfig/conf.o ../scripts/kconfig/conf.c cat ../scripts/kconfig/zconf.tab.c_shipped > scripts/kconfig/zconf.tab.c cat ../scripts/kconfig/zconf.lex.c_shipped > scripts/kconfig/zconf.lex.c cat ../scripts/kconfig/zconf.hash.c_shipped > scripts/kconfig/zconf.hash.c ../scripts/kconfig/conf.c: In function 'check_stdin': ../scripts/kconfig/conf.c:78:3: error: format not a string literal and no format arguments [-Werror=format-security] printf(_("aborted!\n\n")); ^~~~~~ ../scripts/kconfig/conf.c:79:3: error: format not a string literal and no format arguments [-Werror=format-security] printf(_("Console input/output is redirected. ")); ^~~~~~ ../scripts/kconfig/conf.c:80:3: error: format not a string literal and no format arguments [-Werror=format-security] printf(_("Run 'make oldconfig' to update configuration.\n\n")); ^~~~~~ ../scripts/kconfig/conf.c: In function 'conf_askvalue': ../scripts/kconfig/conf.c:90:3: error: format not a string literal and no format arguments [-Werror=format-security] printf(_("(NEW) ")); ^~~~~~ ../scripts/kconfig/conf.c: In function 'conf_choice': ../scripts/kconfig/conf.c:291:5: error: format not a string literal and no format arguments [-Werror=format-security] printf(_(" (NEW)")); ^~~~~~ ../scripts/kconfig/conf.c: In function 'check_conf': ../scripts/kconfig/conf.c:439:6: error: format not a string literal and no format arguments [-Werror=format-security] printf(_("*\n* Restart config...\n*\n")); ^~~~~~ ../scripts/kconfig/conf.c: In function 'main': ../scripts/kconfig/conf.c:641:6: error: format not a string literal and no format arguments [-Werror=format-security] _("\n*** The configuration requires explicit update.\n\n")); ^ ../scripts/kconfig/conf.c:694:4: error: format not a string literal and no format arguments [-Werror=format-security] fprintf(stderr, _("\n*** Error during writing of the configuration.\n\n")); ^~~~~~~ ../scripts/kconfig/conf.c:698:4: error: format not a string literal and no format arguments [-Werror=format-security] fprintf(stderr, _("\n*** Error during update of the configuration.\n\n")); ^~~~~~~ ../scripts/kconfig/conf.c:709:4: error: format not a string literal and no format arguments [-Werror=format-security] fprintf(stderr, _("\n*** Error during writing of the configuration.\n\n")); ^~~~~~~ gcc -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -Wp,-MD,scripts/kconfig/.zconf.tab.o.d -Iscripts/kconfig -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -DCURSES_LOC="<curses.h>" -DLOCALE -DKBUILD_NO_NLS -I../scripts/kconfig -Iscripts/kconfig -c -o scripts/kconfig/zconf.tab.o scripts/kconfig/zconf.tab.c cc1: some warnings being treated as errors

Hi Tom,

On 4 December 2017 at 16:33, Tom Rini trini@konsulko.com wrote:

Hey all,

So it's release day and I've put up v2018.01-rc1. The merge window is now closed and I've updated git and the tarballs are also up now.

I think my patch queue is in OK shape currently, but I need to pick up a few series once I've had a chance to test them more, and I expect a new EFI PR to come along soon too. Once again, I'm going to otherwise try and be pretty strict about what goes in, and more so as time goes on. I will follow the usual rule of an -rc every other Monday and we're looking at release on Jan 8th, 2018.

Thanks all!

-- Tom

I have some patches that are marked as accepted but there was no email and I don't see them in mainline. For example this one:

http://patchwork.ozlabs.org/patch/841455/

Regards, Simon