On Tue, Nov 10, 2020 at 01:18:41PM +0100, Heinrich Schuchardt wrote:
On 11/10/20 1:16 PM, Tom Rini wrote:
On Tue, Nov 10, 2020 at 01:00:06PM +0100, Heinrich Schuchardt wrote:
On 11/10/20 11:41 AM, Andy Shevchenko wrote:
On Tue, Nov 10, 2020 at 12:40 PM Andy Shevchenko andy.shevchenko@gmail.com wrote:
On Tue, Nov 10, 2020 at 12:22 AM Tom Rini trini@konsulko.com wrote:
Hey all,
It's regular release day and I'm back on schedule, so here's -rc2.
There's a few small'ish things outstanding in my queue, and a queue of things building up for -next already. I'm going to try and make sure what I pull in, even when a clean-up, is as close as can be to the obviously correct side of things. Yes, this should always be the case, I'm just going to try and hold myself to expectations a bit harder.
In terms of a changelog, git log --merges v2021.01-rc1..v2021.01-rc2 contains what I've pulled but as always, better PR messages and tags will provide better results here.
I do have my reminders setup for doing -rc releases every other Monday from here on out and final release on January 11th, 2021. Thanks all!
fdt.c is full of
Correction: all of fdt*.c are full of this kind of compiler warnings
scripts/dtc/libfdt/fdt.c: In function ‘fdt_offset_ptr’: scripts/dtc/libfdt/fdt.c:137:18: warning: comparison of integer expressions of different signedness: ‘unsigned int’ and ‘int’ [-Wsign-compare] 137 | if ((absoffset < offset) | ^
Is it known? Is a fix available?
With what compiler version?
GCC 10.2
Fun. Is that the only problem we see with GCC 10.2? I'm tempted to say post v2021.01 is when we move to 10.2 being default, assuming the kernel.org toolchains get upgraded by then. For now I guess I need to grab https://patchwork.ozlabs.org/project/uboot/patch/20201016144250.29106-1-andr... rather than do a full re-sync.