On Tue, Feb 27, 2018 at 03:12:02PM -0800, Guenter Roeck wrote:
> On Tue, Feb 27, 2018 at 07:36:18PM +0100, Greg Kroah-Hartman wrote:
> > On Tue, Feb 27, 2018 at 06:38:59AM -0800, Guenter Roeck wrote:
> > > 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?
> > > >
> > > > Arnd, any ideas?
> > > >
> > >
> > > Missing for m32r: c95f121142a41c951fd62683a5574f2a7b37c573
> > > Missing for microblaze: 71e7673dadfdae0605d4c1f66ecb4b045c79fe0f
> >
> > Thanks, both queued up, and I've pushed out new 4.14.y and 4.15.y trees.
> >
> All builds are confirmed clean. Tested:
>
> v3.18.96-13-g98f6a49
> v4.4.118-22-ge62da23
> v4.9.84-40-g8a6c3b0
> v4.14.22-57-g02ee682
> v4.15.6-66-g53e92b3
Wonderful, thanks for testing all of this and letting me know.
greg k-h