diff options
| author | Will Deacon <[email protected]> | 2018-06-19 13:53:07 +0100 |
|---|---|---|
| committer | Ingo Molnar <[email protected]> | 2018-06-21 12:52:11 +0200 |
| commit | 84038fd98e8e03ec418e3244b98eb248c5349d7e (patch) | |
| tree | fe1ab32b543e23796ca1b6cb9b5b45dbddae8a4e /tools/perf/scripts/python/export-to-sqlite.py | |
| parent | a70cee9737802654bbbddec027d1d57b7ff24a2c (diff) | |
locking/atomics/m68k: Don't use <asm-generic/bitops/lock.h>
<asm-generic/bitops/lock.h> is shortly going to be built on top of the
atomic_long_*() API, which introduces a nasty circular dependency for
m68k where <linux/atomic.h> pulls in <linux/bitops.h> via:
linux/atomic.h
asm/atomic.h
linux/irqflags.h
asm/irqflags.h
linux/preempt.h
asm/preempt.h
asm-generic/preempt.h
linux/thread_info.h
asm/thread_info.h
asm/page.h
asm-generic/getorder.h
linux/log2.h
linux/bitops.h
Since m68k isn't SMP and doesn't support ACQUIRE/RELEASE barriers, we
can just define the lock bitops in terms of the atomic bitops in the
<asm/bitops.h> header.
Signed-off-by: Will Deacon <[email protected]>
Acked-by: Geert Uytterhoeven <[email protected]>
Acked-by: Peter Zijlstra (Intel) <[email protected]>
Cc: Linus Torvalds <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Cc: [email protected]
Cc: [email protected]
Link: https://lore.kernel.org/lkml/[email protected]
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions