Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: [PATCH 4.14 00/54] 4.14.23-stable review
To:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Arnd Bergmann <arnd@arndb.de>
Cc:     linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
        akpm@linux-foundation.org, shuahkh@osg.samsung.com,
        patches@kernelci.org, ben.hutchings@codethink.co.uk,
        lkft-triage@lists.linaro.org, stable@vger.kernel.org
References: <20180226202144.375869933@linuxfoundation.org>
 <d4f09175-d9f0-6251-ef34-14934fce5186@roeck-us.net>
 <20180227130859.GC32493@kroah.com>
From:   Guenter Roeck <linux@roeck-us.net>
Message-ID: <d67ba57f-c6df-b854-9487-70ce95a321f9@roeck-us.net>
Date:   Tue, 27 Feb 2018 06:34:08 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <20180227130859.GC32493@kroah.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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