Re: Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'
From: Peter Zijlstra
Date: Fri Jun 17 2016 - 10:40:09 EST
- Next message: Jarkko Sakkinen: "[PATCH 2/2] tpm_crb: fix address space of the return pointer in crb_map_res()"
- Previous message: Jarkko Sakkinen: "[PATCH 1/2] tpm_vtpm_proxy: fix address space of a user pointer in vtpmx_fops_ioctl()"
- In reply to: Guenter Roeck: "Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'"
- Next in thread: Peter Zijlstra: "Re: Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Jun 17, 2016 at 07:36:56AM -0700, Guenter Roeck wrote:
> Hi Peter,
>
> I am seeing build failures in -next when trying to build arc / arcv2 targets.
>
> arch/arc/include/asm/atomic.h:74:2: error: âSCOND_FAIL_RETRY_VAR_DEFâ undeclared
> arch/arc/include/asm/atomic.h:87:2: error: expected â:â or â)â before âSCOND_FAIL_RETRY_ASMâ
>
> Problems seem to be caused by 'locking/atomic, arch/arc: Implement
> atomic_fetch_{add,sub,and,andnot,or,xor}()'. Both SCOND_FAIL_RETRY_VAR_DEF and
> SCOND_FAIL_RETRY_ASM are undefined.
Crud, I messed up the rebase against the backoff reverts. Lemme go do
fixups.
- Next message: Jarkko Sakkinen: "[PATCH 2/2] tpm_crb: fix address space of the return pointer in crb_map_res()"
- Previous message: Jarkko Sakkinen: "[PATCH 1/2] tpm_vtpm_proxy: fix address space of a user pointer in vtpmx_fops_ioctl()"
- In reply to: Guenter Roeck: "Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'"
- Next in thread: Peter Zijlstra: "Re: Build failures in -next due to 'locking/atomic, arch/arc: Implement atomic_fetch_{add,sub,and,andnot,or,xor}()'"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]