Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-27 Thread Greg Kroah-Hartman 
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

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-27 Thread Greg Kroah-Hartman 
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

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-27 Thread Guenter Roeck 
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

Guenter

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-27 Thread Guenter Roeck 
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

Guenter

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-27 Thread Guenter Roeck 
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.
> 
I started another build to test it; I'll let you know after it is complete.

Guenter

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-27 Thread Guenter Roeck 
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.
> 
I started another build to test it; I'll let you know after it is complete.

Guenter

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-27 Thread Greg Kroah-Hartman 
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.

greg k-h

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-27 Thread Greg Kroah-Hartman 
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.

greg k-h

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-27 Thread Guenter Roeck 

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.



Build results:
total: 145 pass: 141 fail: 4
Failed builds:
m32r:defconfig
microblaze:mmu_defconfig
microblaze:nommu_defconfig
microblaze:allnoconfig
Qemu test results:
total: 127 pass: 127 fail: 0

Details are available at http://kerneltests.org/builders.

Guenter

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-27 Thread Guenter Roeck 

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.



Build results:
total: 145 pass: 141 fail: 4
Failed builds:
m32r:defconfig
microblaze:mmu_defconfig
microblaze:nommu_defconfig
microblaze:allnoconfig
Qemu test results:
total: 127 pass: 127 fail: 0

Details are available at http://kerneltests.org/builders.

Guenter

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-27 Thread Guenter Roeck 

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

Guenter

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-27 Thread Guenter Roeck 

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

Guenter

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-27 Thread Guenter Roeck 

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

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-27 Thread Guenter Roeck 

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

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-27 Thread Greg Kroah-Hartman 
On Mon, Feb 26, 2018 at 01:45:19PM -0800, Tony Lindgren wrote:
> * Guenter Roeck  [180226 21:20]:
> > On Mon, Feb 26, 2018 at 02:58:24PM -0600, Dan Murphy wrote:
> > > Tony L/Greg
> > > 
> > > On 02/26/2018 02: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.
> > > > 
> > > 
> > > We have a build issue on 4.14.22 and can be re-created with this rc as 
> > > well.
> > > 
> > > arch/arm/mach-omap2/omap-secure.o: In function `omap3_save_secure_ram':
> > > omap-secure.c:(.text+0xe4): undefined reference to 
> > > `save_secure_ram_context'
> > > make: *** [vmlinux] Error 1
> > > 
> > > The issue was introduced with the back port of
> > > 
> > > b59a1da647f163d0bf035f823a908b45c357643a ARM: OMAP2+: Fix SRAM virt to 
> > > phys translation for save_secure_ram_context
> > > 
> > Looks like you may have CONFIG_PM disabled, is that correct ?
> > Is there a default configuration that we can use to reproduce
> > the problem ?
> 
> It should be fixed with this commit in mainline kernel:
> 
> 863204cfdae9 ("ARM: omap2: hide omap3_save_secure_ram on non-OMAP3 builds")

Thanks, I'll queue this up in the next round.

greg k-h

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-27 Thread Greg Kroah-Hartman 
On Mon, Feb 26, 2018 at 01:45:19PM -0800, Tony Lindgren wrote:
> * Guenter Roeck  [180226 21:20]:
> > On Mon, Feb 26, 2018 at 02:58:24PM -0600, Dan Murphy wrote:
> > > Tony L/Greg
> > > 
> > > On 02/26/2018 02: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.
> > > > 
> > > 
> > > We have a build issue on 4.14.22 and can be re-created with this rc as 
> > > well.
> > > 
> > > arch/arm/mach-omap2/omap-secure.o: In function `omap3_save_secure_ram':
> > > omap-secure.c:(.text+0xe4): undefined reference to 
> > > `save_secure_ram_context'
> > > make: *** [vmlinux] Error 1
> > > 
> > > The issue was introduced with the back port of
> > > 
> > > b59a1da647f163d0bf035f823a908b45c357643a ARM: OMAP2+: Fix SRAM virt to 
> > > phys translation for save_secure_ram_context
> > > 
> > Looks like you may have CONFIG_PM disabled, is that correct ?
> > Is there a default configuration that we can use to reproduce
> > the problem ?
> 
> It should be fixed with this commit in mainline kernel:
> 
> 863204cfdae9 ("ARM: omap2: hide omap3_save_secure_ram on non-OMAP3 builds")

Thanks, I'll queue this up in the next round.

greg k-h

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-27 Thread Greg Kroah-Hartman 
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?

thanks,

greg k-h

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-27 Thread Greg Kroah-Hartman 
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?

thanks,

greg k-h

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-27 Thread Guenter Roeck 

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).

Guenter

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-27 Thread Guenter Roeck 

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).

Guenter

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-26 Thread Naresh Kamboju 
On 27 February 2018 at 01:51, 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.
>
> The whole patch series can be found in one patch at:
> 
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.23-rc1.gz
> or in the git tree and branch at:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git 
> linux-4.14.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h


Results from Linaro’s test farm.
No regressions on arm64, arm and x86_64.

Summary


kernel: 4.14.23-rc1
git repo: 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
git branch: linux-4.14.y
git commit: 5e118d0b219c87128794e0734ec357f68d2846cb
git describe: v4.14.22-55-g5e118d0b219c
Test details: 
https://qa-reports.linaro.org/lkft/linux-stable-rc-4.14-oe/build/v4.14.22-55-g5e118d0b219c


No regressions (compared to build v4.14.22)

Boards, architectures and test suites:
-

hi6220-hikey - arm64
* boot - pass: 20,
* kselftest - pass: 48, skip: 17
* libhugetlbfs - pass: 90, skip: 1
* ltp-cap_bounds-tests - pass: 2,
* ltp-containers-tests - pass: 64, skip: 17
* ltp-fcntl-locktests-tests - pass: 2,
* ltp-filecaps-tests - pass: 2,
* ltp-fs-tests - pass: 61, skip: 2
* ltp-fs_bind-tests - pass: 2,
* ltp-fs_perms_simple-tests - pass: 19,
* ltp-fsx-tests - pass: 2,
* ltp-hugetlb-tests - pass: 21, skip: 1
* ltp-io-tests - pass: 3,
* ltp-ipc-tests - pass: 9,
* ltp-math-tests - pass: 11,
* ltp-nptl-tests - pass: 2,
* ltp-pty-tests - pass: 4,
* ltp-sched-tests - pass: 10, skip: 4
* ltp-securebits-tests - pass: 4,
* ltp-syscalls-tests - pass: 999, skip: 151
* ltp-timers-tests - pass: 12, skip: 1

juno-r2 - arm64
* boot - pass: 20,
* kselftest - pass: 48, skip: 17
* libhugetlbfs - pass: 90, skip: 1
* ltp-cap_bounds-tests - pass: 2,
* ltp-containers-tests - pass: 64, skip: 17
* ltp-fcntl-locktests-tests - pass: 2,
* ltp-filecaps-tests - pass: 2,
* ltp-fs-tests - pass: 61, skip: 2
* ltp-fs_bind-tests - pass: 2,
* ltp-fs_perms_simple-tests - pass: 19,
* ltp-fsx-tests - pass: 2,
* ltp-hugetlb-tests - pass: 22,
* ltp-io-tests - pass: 3,
* ltp-ipc-tests - pass: 9,
* ltp-math-tests - pass: 11,
* ltp-nptl-tests - pass: 2,
* ltp-pty-tests - pass: 4,
* ltp-sched-tests - pass: 10, skip: 4
* ltp-securebits-tests - pass: 4,
* ltp-syscalls-tests - pass: 1001, skip: 149
* ltp-timers-tests - pass: 12, skip: 1

x15 - arm
* boot - pass: 20,
* kselftest - pass: 45, skip: 19
* libhugetlbfs - pass: 87, skip: 1
* ltp-cap_bounds-tests - pass: 2,
* ltp-containers-tests - pass: 64, skip: 17
* ltp-fcntl-locktests-tests - pass: 2,
* ltp-filecaps-tests - pass: 2,
* ltp-fs-tests - pass: 61, skip: 2
* ltp-fs_bind-tests - pass: 2,
* ltp-fs_perms_simple-tests - pass: 19,
* ltp-fsx-tests - pass: 2,
* ltp-hugetlb-tests - pass: 20, skip: 2
* ltp-io-tests - pass: 3,
* ltp-ipc-tests - pass: 9,
* ltp-math-tests - pass: 11,
* ltp-nptl-tests - pass: 2,
* ltp-pty-tests - pass: 4,
* ltp-sched-tests - pass: 13, skip: 1
* ltp-securebits-tests - pass: 4,
* ltp-syscalls-tests - pass: 1053, skip: 97
* ltp-timers-tests - pass: 12, skip: 1

x86_64
* boot - pass: 20,
* kselftest - pass: 61, skip: 19
* libhugetlbfs - pass: 90, skip: 1
* ltp-cap_bounds-tests - pass: 2,
* ltp-containers-tests - pass: 64, skip: 17
* ltp-fcntl-locktests-tests - pass: 2,
* ltp-filecaps-tests - pass: 2,
* ltp-fs-tests - pass: 62, skip: 1
* ltp-fs_bind-tests - pass: 2,
* ltp-fs_perms_simple-tests - pass: 19,
* ltp-fsx-tests - pass: 2,
* ltp-hugetlb-tests - pass: 22,
* ltp-io-tests - pass: 3,
* ltp-ipc-tests - pass: 9,
* ltp-math-tests - pass: 11,
* ltp-nptl-tests - pass: 2,
* ltp-pty-tests - pass: 4,
* ltp-sched-tests - pass: 9, skip: 5
* ltp-securebits-tests - pass: 4,
* ltp-syscalls-tests - pass: 1031, skip: 119
* ltp-timers-tests - pass: 12, skip: 1

--
Linaro QA (beta)
https://qa-reports.linaro.org

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-26 Thread Naresh Kamboju 
On 27 February 2018 at 01:51, 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.
>
> The whole patch series can be found in one patch at:
> 
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.23-rc1.gz
> or in the git tree and branch at:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git 
> linux-4.14.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h


Results from Linaro’s test farm.
No regressions on arm64, arm and x86_64.

Summary


kernel: 4.14.23-rc1
git repo: 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
git branch: linux-4.14.y
git commit: 5e118d0b219c87128794e0734ec357f68d2846cb
git describe: v4.14.22-55-g5e118d0b219c
Test details: 
https://qa-reports.linaro.org/lkft/linux-stable-rc-4.14-oe/build/v4.14.22-55-g5e118d0b219c


No regressions (compared to build v4.14.22)

Boards, architectures and test suites:
-

hi6220-hikey - arm64
* boot - pass: 20,
* kselftest - pass: 48, skip: 17
* libhugetlbfs - pass: 90, skip: 1
* ltp-cap_bounds-tests - pass: 2,
* ltp-containers-tests - pass: 64, skip: 17
* ltp-fcntl-locktests-tests - pass: 2,
* ltp-filecaps-tests - pass: 2,
* ltp-fs-tests - pass: 61, skip: 2
* ltp-fs_bind-tests - pass: 2,
* ltp-fs_perms_simple-tests - pass: 19,
* ltp-fsx-tests - pass: 2,
* ltp-hugetlb-tests - pass: 21, skip: 1
* ltp-io-tests - pass: 3,
* ltp-ipc-tests - pass: 9,
* ltp-math-tests - pass: 11,
* ltp-nptl-tests - pass: 2,
* ltp-pty-tests - pass: 4,
* ltp-sched-tests - pass: 10, skip: 4
* ltp-securebits-tests - pass: 4,
* ltp-syscalls-tests - pass: 999, skip: 151
* ltp-timers-tests - pass: 12, skip: 1

juno-r2 - arm64
* boot - pass: 20,
* kselftest - pass: 48, skip: 17
* libhugetlbfs - pass: 90, skip: 1
* ltp-cap_bounds-tests - pass: 2,
* ltp-containers-tests - pass: 64, skip: 17
* ltp-fcntl-locktests-tests - pass: 2,
* ltp-filecaps-tests - pass: 2,
* ltp-fs-tests - pass: 61, skip: 2
* ltp-fs_bind-tests - pass: 2,
* ltp-fs_perms_simple-tests - pass: 19,
* ltp-fsx-tests - pass: 2,
* ltp-hugetlb-tests - pass: 22,
* ltp-io-tests - pass: 3,
* ltp-ipc-tests - pass: 9,
* ltp-math-tests - pass: 11,
* ltp-nptl-tests - pass: 2,
* ltp-pty-tests - pass: 4,
* ltp-sched-tests - pass: 10, skip: 4
* ltp-securebits-tests - pass: 4,
* ltp-syscalls-tests - pass: 1001, skip: 149
* ltp-timers-tests - pass: 12, skip: 1

x15 - arm
* boot - pass: 20,
* kselftest - pass: 45, skip: 19
* libhugetlbfs - pass: 87, skip: 1
* ltp-cap_bounds-tests - pass: 2,
* ltp-containers-tests - pass: 64, skip: 17
* ltp-fcntl-locktests-tests - pass: 2,
* ltp-filecaps-tests - pass: 2,
* ltp-fs-tests - pass: 61, skip: 2
* ltp-fs_bind-tests - pass: 2,
* ltp-fs_perms_simple-tests - pass: 19,
* ltp-fsx-tests - pass: 2,
* ltp-hugetlb-tests - pass: 20, skip: 2
* ltp-io-tests - pass: 3,
* ltp-ipc-tests - pass: 9,
* ltp-math-tests - pass: 11,
* ltp-nptl-tests - pass: 2,
* ltp-pty-tests - pass: 4,
* ltp-sched-tests - pass: 13, skip: 1
* ltp-securebits-tests - pass: 4,
* ltp-syscalls-tests - pass: 1053, skip: 97
* ltp-timers-tests - pass: 12, skip: 1

x86_64
* boot - pass: 20,
* kselftest - pass: 61, skip: 19
* libhugetlbfs - pass: 90, skip: 1
* ltp-cap_bounds-tests - pass: 2,
* ltp-containers-tests - pass: 64, skip: 17
* ltp-fcntl-locktests-tests - pass: 2,
* ltp-filecaps-tests - pass: 2,
* ltp-fs-tests - pass: 62, skip: 1
* ltp-fs_bind-tests - pass: 2,
* ltp-fs_perms_simple-tests - pass: 19,
* ltp-fsx-tests - pass: 2,
* ltp-hugetlb-tests - pass: 22,
* ltp-io-tests - pass: 3,
* ltp-ipc-tests - pass: 9,
* ltp-math-tests - pass: 11,
* ltp-nptl-tests - pass: 2,
* ltp-pty-tests - pass: 4,
* ltp-sched-tests - pass: 9, skip: 5
* ltp-securebits-tests - pass: 4,
* ltp-syscalls-tests - pass: 1031, skip: 119
* ltp-timers-tests - pass: 12, skip: 1

--
Linaro QA (beta)
https://qa-reports.linaro.org

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-26 Thread Shuah Khan 
On 02/26/2018 01: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.
> 
> The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.23-rc1.gz
> or in the git tree and branch at:
>   
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git 
> linux-4.14.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h
> 

Compiled and booted on my test system. No dmesg regressions.

thanks,
-- Shuah

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-26 Thread Shuah Khan 
On 02/26/2018 01: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.
> 
> The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.23-rc1.gz
> or in the git tree and branch at:
>   
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git 
> linux-4.14.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h
> 

Compiled and booted on my test system. No dmesg regressions.

thanks,
-- Shuah

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-26 Thread Dan Murphy 
Tony

On 02/26/2018 03:45 PM, Tony Lindgren wrote:
> * Guenter Roeck  [180226 21:20]:
>> On Mon, Feb 26, 2018 at 02:58:24PM -0600, Dan Murphy wrote:
>>> Tony L/Greg
>>>
>>> On 02/26/2018 02: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.

>>>
>>> We have a build issue on 4.14.22 and can be re-created with this rc as well.
>>>
>>> arch/arm/mach-omap2/omap-secure.o: In function `omap3_save_secure_ram':
>>> omap-secure.c:(.text+0xe4): undefined reference to `save_secure_ram_context'
>>> make: *** [vmlinux] Error 1
>>>
>>> The issue was introduced with the back port of
>>>
>>> b59a1da647f163d0bf035f823a908b45c357643a ARM: OMAP2+: Fix SRAM virt to phys 
>>> translation for save_secure_ram_context
>>>
>> Looks like you may have CONFIG_PM disabled, is that correct ?
>> Is there a default configuration that we can use to reproduce
>> the problem ?
> 
> It should be fixed with this commit in mainline kernel:
> 
> 863204cfdae9 ("ARM: omap2: hide omap3_save_secure_ram on non-OMAP3 builds")

Thanks for sharing.  I cherry picked this into the failing build and it built 
successfully.

So can pull this into 4.14.23-rc.  If our "TI next" merge cycle is successful we
should see this error go away.  We missed it last week because the offending 
commit caused
a merge conflict with our TI tree.

I tested this against the multi_v7_defconfig with these CONFIG flags amended.  
Ignoring the override warnings
CONFIG_SOC_AM43XX=y
CONFIG_ARCH_OMAP2PLUS=y
# Disable Socs other than AM43xx
CONFIG_ARCH_OMAP2=n
CONFIG_ARCH_OMAP3=n
CONFIG_ARCH_OMAP4=n
CONFIG_SOC_OMAP5=n
CONFIG_SOC_AM33XX=n
CONFIG_SOC_DRA7XX=n
CONFIG_ARCH_KEYSTONE=n

Tested-by: Dan Murphy 

> 
> Regards,
> 
> Tony
> 


-- 
--
Dan Murphy

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-26 Thread Dan Murphy 
Tony

On 02/26/2018 03:45 PM, Tony Lindgren wrote:
> * Guenter Roeck  [180226 21:20]:
>> On Mon, Feb 26, 2018 at 02:58:24PM -0600, Dan Murphy wrote:
>>> Tony L/Greg
>>>
>>> On 02/26/2018 02: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.

>>>
>>> We have a build issue on 4.14.22 and can be re-created with this rc as well.
>>>
>>> arch/arm/mach-omap2/omap-secure.o: In function `omap3_save_secure_ram':
>>> omap-secure.c:(.text+0xe4): undefined reference to `save_secure_ram_context'
>>> make: *** [vmlinux] Error 1
>>>
>>> The issue was introduced with the back port of
>>>
>>> b59a1da647f163d0bf035f823a908b45c357643a ARM: OMAP2+: Fix SRAM virt to phys 
>>> translation for save_secure_ram_context
>>>
>> Looks like you may have CONFIG_PM disabled, is that correct ?
>> Is there a default configuration that we can use to reproduce
>> the problem ?
> 
> It should be fixed with this commit in mainline kernel:
> 
> 863204cfdae9 ("ARM: omap2: hide omap3_save_secure_ram on non-OMAP3 builds")

Thanks for sharing.  I cherry picked this into the failing build and it built 
successfully.

So can pull this into 4.14.23-rc.  If our "TI next" merge cycle is successful we
should see this error go away.  We missed it last week because the offending 
commit caused
a merge conflict with our TI tree.

I tested this against the multi_v7_defconfig with these CONFIG flags amended.  
Ignoring the override warnings
CONFIG_SOC_AM43XX=y
CONFIG_ARCH_OMAP2PLUS=y
# Disable Socs other than AM43xx
CONFIG_ARCH_OMAP2=n
CONFIG_ARCH_OMAP3=n
CONFIG_ARCH_OMAP4=n
CONFIG_SOC_OMAP5=n
CONFIG_SOC_AM33XX=n
CONFIG_SOC_DRA7XX=n
CONFIG_ARCH_KEYSTONE=n

Tested-by: Dan Murphy 

> 
> Regards,
> 
> Tony
> 


-- 
--
Dan Murphy

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-26 Thread Tony Lindgren 
* Guenter Roeck  [180226 21:20]:
> On Mon, Feb 26, 2018 at 02:58:24PM -0600, Dan Murphy wrote:
> > Tony L/Greg
> > 
> > On 02/26/2018 02: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.
> > > 
> > 
> > We have a build issue on 4.14.22 and can be re-created with this rc as well.
> > 
> > arch/arm/mach-omap2/omap-secure.o: In function `omap3_save_secure_ram':
> > omap-secure.c:(.text+0xe4): undefined reference to `save_secure_ram_context'
> > make: *** [vmlinux] Error 1
> > 
> > The issue was introduced with the back port of
> > 
> > b59a1da647f163d0bf035f823a908b45c357643a ARM: OMAP2+: Fix SRAM virt to phys 
> > translation for save_secure_ram_context
> > 
> Looks like you may have CONFIG_PM disabled, is that correct ?
> Is there a default configuration that we can use to reproduce
> the problem ?

It should be fixed with this commit in mainline kernel:

863204cfdae9 ("ARM: omap2: hide omap3_save_secure_ram on non-OMAP3 builds")

Regards,

Tony

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-26 Thread Tony Lindgren 
* Guenter Roeck  [180226 21:20]:
> On Mon, Feb 26, 2018 at 02:58:24PM -0600, Dan Murphy wrote:
> > Tony L/Greg
> > 
> > On 02/26/2018 02: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.
> > > 
> > 
> > We have a build issue on 4.14.22 and can be re-created with this rc as well.
> > 
> > arch/arm/mach-omap2/omap-secure.o: In function `omap3_save_secure_ram':
> > omap-secure.c:(.text+0xe4): undefined reference to `save_secure_ram_context'
> > make: *** [vmlinux] Error 1
> > 
> > The issue was introduced with the back port of
> > 
> > b59a1da647f163d0bf035f823a908b45c357643a ARM: OMAP2+: Fix SRAM virt to phys 
> > translation for save_secure_ram_context
> > 
> Looks like you may have CONFIG_PM disabled, is that correct ?
> Is there a default configuration that we can use to reproduce
> the problem ?

It should be fixed with this commit in mainline kernel:

863204cfdae9 ("ARM: omap2: hide omap3_save_secure_ram on non-OMAP3 builds")

Regards,

Tony

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-26 Thread Guenter Roeck 
On Mon, Feb 26, 2018 at 02:58:24PM -0600, Dan Murphy wrote:
> Tony L/Greg
> 
> On 02/26/2018 02: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.
> > 
> 
> We have a build issue on 4.14.22 and can be re-created with this rc as well.
> 
> arch/arm/mach-omap2/omap-secure.o: In function `omap3_save_secure_ram':
> omap-secure.c:(.text+0xe4): undefined reference to `save_secure_ram_context'
> make: *** [vmlinux] Error 1
> 
> The issue was introduced with the back port of
> 
> b59a1da647f163d0bf035f823a908b45c357643a ARM: OMAP2+: Fix SRAM virt to phys 
> translation for save_secure_ram_context
> 
Looks like you may have CONFIG_PM disabled, is that correct ?
Is there a default configuration that we can use to reproduce
the problem ?

Guenter

> Dan
> 
> 
> > The whole patch series can be found in one patch at:
> > 
> > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.23-rc1.gz
> > or in the git tree and branch at:
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git 
> > linux-4.14.y
> > and the diffstat can be found below.
> > 
> > thanks,
> > 
> > greg k-h
> > 
> > -
> > Pseudo-Shortlog of commits:
> > 
> > Greg Kroah-Hartman 
> > Linux 4.14.23-rc1
> > 
> > Chris Wilson 
> > drm/i915/breadcrumbs: Ignore unsubmitted signalers
> > 
> > Kai-Heng Feng 
> > drm/amdgpu: add new device to use atpx quirk
> > 
> > Alex Deucher 
> > drm/amdgpu: Avoid leaking PM domain on driver unbind (v2)
> > 
> > Alex Deucher 
> > drm/amdgpu: add atpx quirk handling (v2)
> > 
> > Alex Deucher 
> > drm/amdgpu: only check mmBIF_IOV_FUNC_IDENTIFIER on tonga/fiji
> > 
> > Alex Deucher 
> > drm/amdgpu: Add dpm quirk for Jet PRO (v2)
> > 
> > Huang Rui 
> > drm/amdgpu: disable MMHUB power gating on raven
> > 
> > Chris Wilson 
> > drm: Handle unexpected holes in color-eviction
> > 
> > Daniel Vetter 
> > drm/cirrus: Load lut in crtc_commit
> > 
> > Yoshihiro Shimoda 
> > usb: renesas_usbhs: missed the "running" flag in usb_dmac with rx path
> > 
> > Jack Pham 
> > usb: gadget: f_fs: Use config_ep_by_speed()
> > 
> > Jack Pham 
> > usb: gadget: f_fs: Process all descriptors during bind
> > 
> > Bin Liu 
> > Revert "usb: musb: host: don't start next rx urb if current one failed"
> > 
> > Karsten Koop 
> > usb: ldusb: add PIDs for new CASSY devices supported by this driver
> > 
> > Thinh Nguyen 
> > usb: dwc3: ep0: Reset TRB counter for ep0 IN
> > 
> > Thinh Nguyen 
> > usb: dwc3: gadget: Set maxpacket size for ep0 IN
> > 
> > Peter Chen 
> > usb: host: ehci: use correct device pointer for dma ops
> > 
> > Kai-Heng Feng 
> > drm/edid: Add 6 bpc quirk for CPT panel in Asus UX303LA
> > 
> > Jack Stocker 
> > Add delay-init quirk for Corsair K70 RGB keyboards
> > 
> > Will Deacon 
> > arm64: cpufeature: Fix CTR_EL0 field definitions
> > 
> > Michael Weiser 
> > arm64: Disable unhandled signal log messages by default
> > 
> > Michael Weiser 
> > arm64: Remove unimplemented syscall log message
> > 
> > AMAN DEEP 
> > usb: ohci: Proper handling of ed_rm_list to handle race condition 
> > between usb_kill_urb() and finish_unlinks()
> > 
> > Shigeru Yoshida 
> > ohci-hcd: Fix race condition caused by ohci_urb_enqueue() and 
> > io_watchdog_func()
> > 
> > Casey Leedom 
> > PCI/cxgb4: Extend T3 PCI quirk to T4+ devices
> > 
> > Matt Redfearn 
> > irqchip/mips-gic: Avoid spuriously handling masked interrupts
> > 
> > Shanker Donthineni 
> > irqchip/gic-v3: Use wmb() instead of smb_wmb() in gic_raise_softirq()
> > 
> > Huang Ying 
> > mm, swap, frontswap: fix THP swap if frontswap enabled
> > 
> > Arnd Bergmann 
> > x86/oprofile: Fix bogus GCC-8 warning in nmi_setup()
> > 
> > Arnd Bergmann 
> > Kbuild: always define endianess in kconfig.h
> > 
> > Lars-Peter Clausen

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-26 Thread Guenter Roeck 
On Mon, Feb 26, 2018 at 02:58:24PM -0600, Dan Murphy wrote:
> Tony L/Greg
> 
> On 02/26/2018 02: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.
> > 
> 
> We have a build issue on 4.14.22 and can be re-created with this rc as well.
> 
> arch/arm/mach-omap2/omap-secure.o: In function `omap3_save_secure_ram':
> omap-secure.c:(.text+0xe4): undefined reference to `save_secure_ram_context'
> make: *** [vmlinux] Error 1
> 
> The issue was introduced with the back port of
> 
> b59a1da647f163d0bf035f823a908b45c357643a ARM: OMAP2+: Fix SRAM virt to phys 
> translation for save_secure_ram_context
> 
Looks like you may have CONFIG_PM disabled, is that correct ?
Is there a default configuration that we can use to reproduce
the problem ?

Guenter

> Dan
> 
> 
> > The whole patch series can be found in one patch at:
> > 
> > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.23-rc1.gz
> > or in the git tree and branch at:
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git 
> > linux-4.14.y
> > and the diffstat can be found below.
> > 
> > thanks,
> > 
> > greg k-h
> > 
> > -
> > Pseudo-Shortlog of commits:
> > 
> > Greg Kroah-Hartman 
> > Linux 4.14.23-rc1
> > 
> > Chris Wilson 
> > drm/i915/breadcrumbs: Ignore unsubmitted signalers
> > 
> > Kai-Heng Feng 
> > drm/amdgpu: add new device to use atpx quirk
> > 
> > Alex Deucher 
> > drm/amdgpu: Avoid leaking PM domain on driver unbind (v2)
> > 
> > Alex Deucher 
> > drm/amdgpu: add atpx quirk handling (v2)
> > 
> > Alex Deucher 
> > drm/amdgpu: only check mmBIF_IOV_FUNC_IDENTIFIER on tonga/fiji
> > 
> > Alex Deucher 
> > drm/amdgpu: Add dpm quirk for Jet PRO (v2)
> > 
> > Huang Rui 
> > drm/amdgpu: disable MMHUB power gating on raven
> > 
> > Chris Wilson 
> > drm: Handle unexpected holes in color-eviction
> > 
> > Daniel Vetter 
> > drm/cirrus: Load lut in crtc_commit
> > 
> > Yoshihiro Shimoda 
> > usb: renesas_usbhs: missed the "running" flag in usb_dmac with rx path
> > 
> > Jack Pham 
> > usb: gadget: f_fs: Use config_ep_by_speed()
> > 
> > Jack Pham 
> > usb: gadget: f_fs: Process all descriptors during bind
> > 
> > Bin Liu 
> > Revert "usb: musb: host: don't start next rx urb if current one failed"
> > 
> > Karsten Koop 
> > usb: ldusb: add PIDs for new CASSY devices supported by this driver
> > 
> > Thinh Nguyen 
> > usb: dwc3: ep0: Reset TRB counter for ep0 IN
> > 
> > Thinh Nguyen 
> > usb: dwc3: gadget: Set maxpacket size for ep0 IN
> > 
> > Peter Chen 
> > usb: host: ehci: use correct device pointer for dma ops
> > 
> > Kai-Heng Feng 
> > drm/edid: Add 6 bpc quirk for CPT panel in Asus UX303LA
> > 
> > Jack Stocker 
> > Add delay-init quirk for Corsair K70 RGB keyboards
> > 
> > Will Deacon 
> > arm64: cpufeature: Fix CTR_EL0 field definitions
> > 
> > Michael Weiser 
> > arm64: Disable unhandled signal log messages by default
> > 
> > Michael Weiser 
> > arm64: Remove unimplemented syscall log message
> > 
> > AMAN DEEP 
> > usb: ohci: Proper handling of ed_rm_list to handle race condition 
> > between usb_kill_urb() and finish_unlinks()
> > 
> > Shigeru Yoshida 
> > ohci-hcd: Fix race condition caused by ohci_urb_enqueue() and 
> > io_watchdog_func()
> > 
> > Casey Leedom 
> > PCI/cxgb4: Extend T3 PCI quirk to T4+ devices
> > 
> > Matt Redfearn 
> > irqchip/mips-gic: Avoid spuriously handling masked interrupts
> > 
> > Shanker Donthineni 
> > irqchip/gic-v3: Use wmb() instead of smb_wmb() in gic_raise_softirq()
> > 
> > Huang Ying 
> > mm, swap, frontswap: fix THP swap if frontswap enabled
> > 
> > Arnd Bergmann 
> > x86/oprofile: Fix bogus GCC-8 warning in nmi_setup()
> > 
> > Arnd Bergmann 
> > Kbuild: always define endianess in kconfig.h
> > 
> > Lars-Peter Clausen 
> > iio: adis_lib: Initialize trigger before requesting interrupt
> > 
> > Stefan Windfeldt-Prytz 
> > iio: buffer: check if a buffer has been set up when poll is called
> > 
> > Andreas Klinger 
> > iio: srf08: fix link error "devm_iio_triggered_buffer_setup" undefined
> > 
> > Fabrice Gasnier 
> > iio: adc: stm32: fix stm32h7_adc_enable error handling
> > 
> > Leon Romanovsky 
> > RDMA/uverbs: Sanitize user entered port numbers prior to access it
> > 
> > Leon Romanovsky 
> > RDMA/uverbs: Fix circular locking dependency
> > 
> > Leon Romanovsky 
> > RDMA/uverbs: Fix bad unlock balance in ib_uverbs_close_xrcd
> > 
> > Leon Romanovsky 
> > RDMA/uverbs: Protect from command mask overflow
> > 
> > Leon Romanovsky 
> >

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-26 Thread Dan Murphy 
Tony L/Greg

On 02/26/2018 02: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.
> 

We have a build issue on 4.14.22 and can be re-created with this rc as well.

arch/arm/mach-omap2/omap-secure.o: In function `omap3_save_secure_ram':
omap-secure.c:(.text+0xe4): undefined reference to `save_secure_ram_context'
make: *** [vmlinux] Error 1

The issue was introduced with the back port of

b59a1da647f163d0bf035f823a908b45c357643a ARM: OMAP2+: Fix SRAM virt to phys 
translation for save_secure_ram_context

Dan


> The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.23-rc1.gz
> or in the git tree and branch at:
>   
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git 
> linux-4.14.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h
> 
> -
> Pseudo-Shortlog of commits:
> 
> Greg Kroah-Hartman 
> Linux 4.14.23-rc1
> 
> Chris Wilson 
> drm/i915/breadcrumbs: Ignore unsubmitted signalers
> 
> Kai-Heng Feng 
> drm/amdgpu: add new device to use atpx quirk
> 
> Alex Deucher 
> drm/amdgpu: Avoid leaking PM domain on driver unbind (v2)
> 
> Alex Deucher 
> drm/amdgpu: add atpx quirk handling (v2)
> 
> Alex Deucher 
> drm/amdgpu: only check mmBIF_IOV_FUNC_IDENTIFIER on tonga/fiji
> 
> Alex Deucher 
> drm/amdgpu: Add dpm quirk for Jet PRO (v2)
> 
> Huang Rui 
> drm/amdgpu: disable MMHUB power gating on raven
> 
> Chris Wilson 
> drm: Handle unexpected holes in color-eviction
> 
> Daniel Vetter 
> drm/cirrus: Load lut in crtc_commit
> 
> Yoshihiro Shimoda 
> usb: renesas_usbhs: missed the "running" flag in usb_dmac with rx path
> 
> Jack Pham 
> usb: gadget: f_fs: Use config_ep_by_speed()
> 
> Jack Pham 
> usb: gadget: f_fs: Process all descriptors during bind
> 
> Bin Liu 
> Revert "usb: musb: host: don't start next rx urb if current one failed"
> 
> Karsten Koop 
> usb: ldusb: add PIDs for new CASSY devices supported by this driver
> 
> Thinh Nguyen 
> usb: dwc3: ep0: Reset TRB counter for ep0 IN
> 
> Thinh Nguyen 
> usb: dwc3: gadget: Set maxpacket size for ep0 IN
> 
> Peter Chen 
> usb: host: ehci: use correct device pointer for dma ops
> 
> Kai-Heng Feng 
> drm/edid: Add 6 bpc quirk for CPT panel in Asus UX303LA
> 
> Jack Stocker 
> Add delay-init quirk for Corsair K70 RGB keyboards
> 
> Will Deacon 
> arm64: cpufeature: Fix CTR_EL0 field definitions
> 
> Michael Weiser 
> arm64: Disable unhandled signal log messages by default
> 
> Michael Weiser 
> arm64: Remove unimplemented syscall log message
> 
> AMAN DEEP 
> usb: ohci: Proper handling of ed_rm_list to handle race condition between 
> usb_kill_urb() and finish_unlinks()
> 
> Shigeru Yoshida 
> ohci-hcd: Fix race condition caused by ohci_urb_enqueue() and 
> io_watchdog_func()
> 
> Casey Leedom 
> PCI/cxgb4: Extend T3 PCI quirk to T4+ devices
> 
> Matt Redfearn 
> irqchip/mips-gic: Avoid spuriously handling masked interrupts
> 
> Shanker Donthineni 
> irqchip/gic-v3: Use wmb() instead of smb_wmb() in gic_raise_softirq()
> 
> Huang Ying 
> mm, swap, frontswap: fix THP swap if frontswap enabled
> 
> Arnd Bergmann 
> x86/oprofile: Fix bogus GCC-8 warning in nmi_setup()
> 
> Arnd Bergmann 
> Kbuild: always define endianess in kconfig.h
> 
> Lars-Peter Clausen 
> iio: adis_lib: Initialize trigger before requesting interrupt
> 
> Stefan Windfeldt-Prytz 
> iio: buffer: check if a buffer has been set up when poll is called
> 
> Andreas Klinger 
> iio: srf08: fix link error "devm_iio_triggered_buffer_setup" undefined
> 
> Fabrice Gasnier 
> iio: adc: stm32: fix stm32h7_adc_enable error handling
> 
> Leon Romanovsky 
>

Re: [PATCH 4.14 00/54] 4.14.23-stable review

2018-02-26 Thread Dan Murphy 
Tony L/Greg

On 02/26/2018 02: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.
> 

We have a build issue on 4.14.22 and can be re-created with this rc as well.

arch/arm/mach-omap2/omap-secure.o: In function `omap3_save_secure_ram':
omap-secure.c:(.text+0xe4): undefined reference to `save_secure_ram_context'
make: *** [vmlinux] Error 1

The issue was introduced with the back port of

b59a1da647f163d0bf035f823a908b45c357643a ARM: OMAP2+: Fix SRAM virt to phys 
translation for save_secure_ram_context

Dan


> The whole patch series can be found in one patch at:
>   
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.23-rc1.gz
> or in the git tree and branch at:
>   
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git 
> linux-4.14.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h
> 
> -
> Pseudo-Shortlog of commits:
> 
> Greg Kroah-Hartman 
> Linux 4.14.23-rc1
> 
> Chris Wilson 
> drm/i915/breadcrumbs: Ignore unsubmitted signalers
> 
> Kai-Heng Feng 
> drm/amdgpu: add new device to use atpx quirk
> 
> Alex Deucher 
> drm/amdgpu: Avoid leaking PM domain on driver unbind (v2)
> 
> Alex Deucher 
> drm/amdgpu: add atpx quirk handling (v2)
> 
> Alex Deucher 
> drm/amdgpu: only check mmBIF_IOV_FUNC_IDENTIFIER on tonga/fiji
> 
> Alex Deucher 
> drm/amdgpu: Add dpm quirk for Jet PRO (v2)
> 
> Huang Rui 
> drm/amdgpu: disable MMHUB power gating on raven
> 
> Chris Wilson 
> drm: Handle unexpected holes in color-eviction
> 
> Daniel Vetter 
> drm/cirrus: Load lut in crtc_commit
> 
> Yoshihiro Shimoda 
> usb: renesas_usbhs: missed the "running" flag in usb_dmac with rx path
> 
> Jack Pham 
> usb: gadget: f_fs: Use config_ep_by_speed()
> 
> Jack Pham 
> usb: gadget: f_fs: Process all descriptors during bind
> 
> Bin Liu 
> Revert "usb: musb: host: don't start next rx urb if current one failed"
> 
> Karsten Koop 
> usb: ldusb: add PIDs for new CASSY devices supported by this driver
> 
> Thinh Nguyen 
> usb: dwc3: ep0: Reset TRB counter for ep0 IN
> 
> Thinh Nguyen 
> usb: dwc3: gadget: Set maxpacket size for ep0 IN
> 
> Peter Chen 
> usb: host: ehci: use correct device pointer for dma ops
> 
> Kai-Heng Feng 
> drm/edid: Add 6 bpc quirk for CPT panel in Asus UX303LA
> 
> Jack Stocker 
> Add delay-init quirk for Corsair K70 RGB keyboards
> 
> Will Deacon 
> arm64: cpufeature: Fix CTR_EL0 field definitions
> 
> Michael Weiser 
> arm64: Disable unhandled signal log messages by default
> 
> Michael Weiser 
> arm64: Remove unimplemented syscall log message
> 
> AMAN DEEP 
> usb: ohci: Proper handling of ed_rm_list to handle race condition between 
> usb_kill_urb() and finish_unlinks()
> 
> Shigeru Yoshida 
> ohci-hcd: Fix race condition caused by ohci_urb_enqueue() and 
> io_watchdog_func()
> 
> Casey Leedom 
> PCI/cxgb4: Extend T3 PCI quirk to T4+ devices
> 
> Matt Redfearn 
> irqchip/mips-gic: Avoid spuriously handling masked interrupts
> 
> Shanker Donthineni 
> irqchip/gic-v3: Use wmb() instead of smb_wmb() in gic_raise_softirq()
> 
> Huang Ying 
> mm, swap, frontswap: fix THP swap if frontswap enabled
> 
> Arnd Bergmann 
> x86/oprofile: Fix bogus GCC-8 warning in nmi_setup()
> 
> Arnd Bergmann 
> Kbuild: always define endianess in kconfig.h
> 
> Lars-Peter Clausen 
> iio: adis_lib: Initialize trigger before requesting interrupt
> 
> Stefan Windfeldt-Prytz 
> iio: buffer: check if a buffer has been set up when poll is called
> 
> Andreas Klinger 
> iio: srf08: fix link error "devm_iio_triggered_buffer_setup" undefined
> 
> Fabrice Gasnier 
> iio: adc: stm32: fix stm32h7_adc_enable error handling
> 
> Leon Romanovsky 
> RDMA/uverbs: Sanitize user entered port numbers prior to access it
> 
> Leon Romanovsky 
> RDMA/uverbs: Fix circular locking dependency
> 
> Leon Romanovsky 
> RDMA/uverbs: Fix bad unlock balance in ib_uverbs_close_xrcd
> 
> Leon Romanovsky 
> RDMA/uverbs: Protect from command mask overflow
> 
> Leon Romanovsky 
> RDMA/uverbs: Protect from races between lookup and destroy of uobjects
> 
> Hans de Goede 
> extcon: int3496: process id-pin first so that we start with the right 
> status
> 
> Eric Biggers 
> PKCS#7: fix certificate blacklisting
> 
> Eric Biggers 
> PKCS#7: fix certificate chain verification
> 
> Eric Biggers 
> X.509: fix NULL dereference when restricting key with unsupported_sig
> 
> Eric Biggers 
> X.509: fix BUG_ON() when hash algorithm is unsupported
> 
> Eric Anholt 
> i2c: bcm2835: Set up the

[PATCH 4.14 00/54] 4.14.23-stable review

2018-02-26 Thread Greg Kroah-Hartman 
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.

The whole patch series can be found in one patch at:

https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.23-rc1.gz
or in the git tree and branch at:

git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git 
linux-4.14.y
and the diffstat can be found below.

thanks,

greg k-h

-
Pseudo-Shortlog of commits:

Greg Kroah-Hartman 
Linux 4.14.23-rc1

Chris Wilson 
drm/i915/breadcrumbs: Ignore unsubmitted signalers

Kai-Heng Feng 
drm/amdgpu: add new device to use atpx quirk

Alex Deucher 
drm/amdgpu: Avoid leaking PM domain on driver unbind (v2)

Alex Deucher 
drm/amdgpu: add atpx quirk handling (v2)

Alex Deucher 
drm/amdgpu: only check mmBIF_IOV_FUNC_IDENTIFIER on tonga/fiji

Alex Deucher 
drm/amdgpu: Add dpm quirk for Jet PRO (v2)

Huang Rui 
drm/amdgpu: disable MMHUB power gating on raven

Chris Wilson 
drm: Handle unexpected holes in color-eviction

Daniel Vetter 
drm/cirrus: Load lut in crtc_commit

Yoshihiro Shimoda 
usb: renesas_usbhs: missed the "running" flag in usb_dmac with rx path

Jack Pham 
usb: gadget: f_fs: Use config_ep_by_speed()

Jack Pham 
usb: gadget: f_fs: Process all descriptors during bind

Bin Liu 
Revert "usb: musb: host: don't start next rx urb if current one failed"

Karsten Koop 
usb: ldusb: add PIDs for new CASSY devices supported by this driver

Thinh Nguyen 
usb: dwc3: ep0: Reset TRB counter for ep0 IN

Thinh Nguyen 
usb: dwc3: gadget: Set maxpacket size for ep0 IN

Peter Chen 
usb: host: ehci: use correct device pointer for dma ops

Kai-Heng Feng 
drm/edid: Add 6 bpc quirk for CPT panel in Asus UX303LA

Jack Stocker 
Add delay-init quirk for Corsair K70 RGB keyboards

Will Deacon 
arm64: cpufeature: Fix CTR_EL0 field definitions

Michael Weiser 
arm64: Disable unhandled signal log messages by default

Michael Weiser 
arm64: Remove unimplemented syscall log message

AMAN DEEP 
usb: ohci: Proper handling of ed_rm_list to handle race condition between 
usb_kill_urb() and finish_unlinks()

Shigeru Yoshida 
ohci-hcd: Fix race condition caused by ohci_urb_enqueue() and 
io_watchdog_func()

Casey Leedom 
PCI/cxgb4: Extend T3 PCI quirk to T4+ devices

Matt Redfearn 
irqchip/mips-gic: Avoid spuriously handling masked interrupts

Shanker Donthineni 
irqchip/gic-v3: Use wmb() instead of smb_wmb() in gic_raise_softirq()

Huang Ying 
mm, swap, frontswap: fix THP swap if frontswap enabled

Arnd Bergmann 
x86/oprofile: Fix bogus GCC-8 warning in nmi_setup()

Arnd Bergmann 
Kbuild: always define endianess in kconfig.h

Lars-Peter Clausen 
iio: adis_lib: Initialize trigger before requesting interrupt

Stefan Windfeldt-Prytz 
iio: buffer: check if a buffer has been set up when poll is called

Andreas Klinger 
iio: srf08: fix link error "devm_iio_triggered_buffer_setup" undefined

Fabrice Gasnier 
iio: adc: stm32: fix stm32h7_adc_enable error handling

Leon Romanovsky 
RDMA/uverbs: Sanitize user entered port numbers prior to access it

Leon Romanovsky 
RDMA/uverbs: Fix circular locking dependency

Leon Romanovsky 
RDMA/uverbs: Fix bad unlock balance in ib_uverbs_close_xrcd

Leon Romanovsky 
RDMA/uverbs: Protect from command mask overflow

Leon Romanovsky 
RDMA/uverbs: Protect from races between lookup and destroy of uobjects

Hans de Goede 
extcon: int3496: process id-pin first so that we start with the right status

Eric Biggers 
PKCS#7: fix certificate blacklisting

Eric Biggers 
PKCS#7: fix certificate chain verification

Eric Biggers

[PATCH 4.14 00/54] 4.14.23-stable review

2018-02-26 Thread Greg Kroah-Hartman 
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.

The whole patch series can be found in one patch at:

https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.23-rc1.gz
or in the git tree and branch at:

git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git 
linux-4.14.y
and the diffstat can be found below.

thanks,

greg k-h

-
Pseudo-Shortlog of commits:

Greg Kroah-Hartman 
Linux 4.14.23-rc1

Chris Wilson 
drm/i915/breadcrumbs: Ignore unsubmitted signalers

Kai-Heng Feng 
drm/amdgpu: add new device to use atpx quirk

Alex Deucher 
drm/amdgpu: Avoid leaking PM domain on driver unbind (v2)

Alex Deucher 
drm/amdgpu: add atpx quirk handling (v2)

Alex Deucher 
drm/amdgpu: only check mmBIF_IOV_FUNC_IDENTIFIER on tonga/fiji

Alex Deucher 
drm/amdgpu: Add dpm quirk for Jet PRO (v2)

Huang Rui 
drm/amdgpu: disable MMHUB power gating on raven

Chris Wilson 
drm: Handle unexpected holes in color-eviction

Daniel Vetter 
drm/cirrus: Load lut in crtc_commit

Yoshihiro Shimoda 
usb: renesas_usbhs: missed the "running" flag in usb_dmac with rx path

Jack Pham 
usb: gadget: f_fs: Use config_ep_by_speed()

Jack Pham 
usb: gadget: f_fs: Process all descriptors during bind

Bin Liu 
Revert "usb: musb: host: don't start next rx urb if current one failed"

Karsten Koop 
usb: ldusb: add PIDs for new CASSY devices supported by this driver

Thinh Nguyen 
usb: dwc3: ep0: Reset TRB counter for ep0 IN

Thinh Nguyen 
usb: dwc3: gadget: Set maxpacket size for ep0 IN

Peter Chen 
usb: host: ehci: use correct device pointer for dma ops

Kai-Heng Feng 
drm/edid: Add 6 bpc quirk for CPT panel in Asus UX303LA

Jack Stocker 
Add delay-init quirk for Corsair K70 RGB keyboards

Will Deacon 
arm64: cpufeature: Fix CTR_EL0 field definitions

Michael Weiser 
arm64: Disable unhandled signal log messages by default

Michael Weiser 
arm64: Remove unimplemented syscall log message

AMAN DEEP 
usb: ohci: Proper handling of ed_rm_list to handle race condition between 
usb_kill_urb() and finish_unlinks()

Shigeru Yoshida 
ohci-hcd: Fix race condition caused by ohci_urb_enqueue() and 
io_watchdog_func()

Casey Leedom 
PCI/cxgb4: Extend T3 PCI quirk to T4+ devices

Matt Redfearn 
irqchip/mips-gic: Avoid spuriously handling masked interrupts

Shanker Donthineni 
irqchip/gic-v3: Use wmb() instead of smb_wmb() in gic_raise_softirq()

Huang Ying 
mm, swap, frontswap: fix THP swap if frontswap enabled

Arnd Bergmann 
x86/oprofile: Fix bogus GCC-8 warning in nmi_setup()

Arnd Bergmann 
Kbuild: always define endianess in kconfig.h

Lars-Peter Clausen 
iio: adis_lib: Initialize trigger before requesting interrupt

Stefan Windfeldt-Prytz 
iio: buffer: check if a buffer has been set up when poll is called

Andreas Klinger 
iio: srf08: fix link error "devm_iio_triggered_buffer_setup" undefined

Fabrice Gasnier 
iio: adc: stm32: fix stm32h7_adc_enable error handling

Leon Romanovsky 
RDMA/uverbs: Sanitize user entered port numbers prior to access it

Leon Romanovsky 
RDMA/uverbs: Fix circular locking dependency

Leon Romanovsky 
RDMA/uverbs: Fix bad unlock balance in ib_uverbs_close_xrcd

Leon Romanovsky 
RDMA/uverbs: Protect from command mask overflow

Leon Romanovsky 
RDMA/uverbs: Protect from races between lookup and destroy of uobjects

Hans de Goede 
extcon: int3496: process id-pin first so that we start with the right status

Eric Biggers 
PKCS#7: fix certificate blacklisting

Eric Biggers 
PKCS#7: fix certificate chain verification

Eric Biggers 
X.509: fix NULL dereference when restricting key with unsupported_sig

Eric Biggers 
X.509: fix BUG_ON() when hash algorithm is unsupported

Eric Anholt 
i2c: bcm2835: Set up the rising/falling edge delays

Ben Gardner 
i2c: designware: must wait for enable

Arnd Bergmann 
cfg80211: fix cfg80211_beacon_dup

James Hogan 
MIPS: Drop spurious __unused in struct compat_flock

Tyrel Datwyler 
scsi: ibmvfc: fix misdefined reserved field in ibmvfc_fcp_rsp_info

Max Filippov 
xtensa: fix high memory/reserved memory collision

Kees Cook 
MIPS: boot: Define __ASSEMBLY__ for its.S build

Kees Cook 
kconfig.h: Include compiler types to avoid missed struct attributes

Ard Biesheuvel 
arm64: mm: don't write garbage into TTBR1_EL1 register

Paolo Abeni 
netfilter: drop outermost socket lock in getsockopt()


-

Diffstat:

 Makefile |  4 +-
 arch/arm64/kernel/cpufeature.c   |  6 +-