Messages in this thread | | | Subject | Re: [PATCH 4.14 00/54] 4.14.23-stable review | From | Guenter Roeck <> | Date | Tue, 27 Feb 2018 06:34:08 -0800 |
| |
On 02/27/2018 05:08 AM, Greg Kroah-Hartman wrote: > On Tue, Feb 27, 2018 at 02:59:39AM -0800, Guenter Roeck wrote: >> On 02/26/2018 12:21 PM, Greg Kroah-Hartman wrote: >>> This is the start of the stable review cycle for the 4.14.23 release. >>> There are 54 patches in this series, all will be posted as a response >>> to this one. If anyone has any issues with these being applied, please >>> let me know. >>> >>> Responses should be made by Wed Feb 28 20:21:22 UTC 2018. >>> Anything received after that time might be too late. >>> >> >> microblaze, m32r: >> >> include/linux/byteorder/big_endian.h:8:2: warning: #warning inconsistent configuration, needs CONFIG_CPU_BIG_ENDIAN [-Wcpp] >> #warning inconsistent configuration, needs CONFIG_CPU_BIG_ENDIAN >> ^~~~~~~ >> /opt/buildbot/slave/stable-queue-4.14/build/lib/find_bit.c:176:15: error: redefinition of ‘find_next_zero_bit_le’ >> >> v4.15 is also affected (m32r builds in v4.15, though, for some reason). > > This sounds like Arnd's Kbuild change 101110f6271c ("Kbuild: always > define endianess in kconfig.h") > > Does this problem also show up in Linus's tree? >
No. My guess would be that some context patches are missing in the older kernels.
I also get lots of
include/linux/byteorder/big_endian.h:8:2: warning: #warning inconsistent configuration, needs CONFIG_CPU_BIG_ENDIAN
which as it turns out is also seen in v4.14.22, meaning the actual problem was most likely introduced earlier (I don't see that warning upstream).
Guenter
| |