Re: [PATCH v2 4/4] locking/atomic: hexagon: arch_cmpxchg[64]_local undefined

2023-11-07 Thread Google
On Sat, 4 Nov 2023 17:16:15 +0800 "wuqiang.matt" wrote: > For architectures that support native cmpxchg, we'd like to > implement arch_cmpxchg[64]_local with the native variants of > supported data size. If not, the generci_cmpxchg[64]_local > will be used. > > Reported-by: kernel test robot >

Re: [PATCH v2 3/4] locking/atomic: openrisc: arch_cmpxchg[64]_local undefined

2023-11-07 Thread Google
On Sat, 4 Nov 2023 17:16:14 +0800 "wuqiang.matt" wrote: > For architectures that support native cmpxchg, we'd like to > implement arch_cmpxchg[64]_local with the native variants of > supported data size. If not, the generci_cmpxchg[64]_local > will be used. Looks good to me. Reviewed-by: Masa

Re: [PATCH v2 2/4] locking/atomic: arc: arch_cmpxchg[64]_local undefined

2023-11-07 Thread Google
On Sat, 4 Nov 2023 17:16:13 +0800 "wuqiang.matt" wrote: > For architectures that support native cmpxchg, we'd like to > implement arch_cmpxchg[64]_local with the native variants of > supported data size. If not, the generci_cmpxchg[64]_local > will be used. > Looks good to me. Reviewed-by: Ma

Re: [PATCH v2 1/4] locking/atomic: arc: data size checking in arch_cmpxchg

2023-11-07 Thread Google
On Sat, 4 Nov 2023 17:16:12 +0800 "wuqiang.matt" wrote: > Macro __cmpxchg() renamed to __cmpxchg_32() to emphasize it's explicit > support of 32bit data size, BUILD_BUG_ON() added to avoid any possible > misuses with unsupported data types. > > In case CONFIG_ARC_HAS_LLSC is undefined, arch_cmp