diff options
author | Arnd Bergmann <arnd@arndb.de> | 2021-12-03 09:07:56 +0100 |
---|---|---|
committer | Thomas Gleixner <tglx@linutronix.de> | 2021-12-11 23:31:51 +0100 |
commit | 0f09c274698590d508c43f924d9dffc7130b782d (patch) | |
tree | 38b9923a8f6f488b2826cd45c3e80f61eaa2e271 /include/linux/vringh.h | |
parent | 77993b595ada5731e513eb06a0f4bf4b9f1e9532 (diff) | |
download | linux-0f09c274698590d508c43f924d9dffc7130b782d.tar.gz linux-0f09c274698590d508c43f924d9dffc7130b782d.tar.bz2 linux-0f09c274698590d508c43f924d9dffc7130b782d.zip |
futex: Fix additional regressions
Naresh reported another architecture that was broken by the same typo that
was already fixed for three architectures: mips also refers to the
futex_atomic_op_inuser_local() function by the wrong name and runs into a
missing closing '}' as well.
Going through the source tree the same typo was found in the documentation
as well as in the xtensa code, both of which ended up escaping the
regression testing so far. In the case of xtensa, it appears that the
broken code path is only used when building for platforms that are not
supported by the default gcc configuration, so they are impossible to test
for with default setups.
After going through these more carefully and fixing up the typos, all
architectures have been build-tested again to ensure that this is now
complete.
Fixes: 4e0d84634445 ("futex: Fix sparc32/m68k/nds32 build regression")
Fixes: 3f2bedabb62c ("futex: Ensure futex_atomic_cmpxchg_inatomic() is present")
Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
Reported-by: Naresh Kamboju <naresh.kamboju@linaro.org>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lore.kernel.org/r/20211203080823.2938839-1-arnd@kernel.org
Diffstat (limited to 'include/linux/vringh.h')
0 files changed, 0 insertions, 0 deletions