diff options
| author | Arnd Bergmann <[email protected]> | 2016-11-16 16:39:05 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2016-11-16 18:30:46 +0100 |
| commit | b826d73b3024485677163253b59ef9bd187ff765 (patch) | |
| tree | 9988b08f99263000cfdc0a13d6d2875fca1fa046 /tools/perf/scripts/python | |
| parent | 735bb39ca3bed8469b3b3a42d8cc57bdb9fc4dd7 (diff) | |
staging: vc04_services: remove duplicate mutex_lock_interruptible
The driver tries to redefine mutex_lock_interruptible as an open-coded
mutex_lock_killable, but that definition clashes with the normal
mutex_lock_interruptible definition when CONFIG_DEBUG_LOCK_ALLOC
is set:
staging/vc04_services/interface/vchiq_arm/vchiq_killable.h:67:0: error: "mutex_lock_interruptible" redefined [-Werror]
#define mutex_lock_interruptible mutex_lock_interruptible_killable
include/linux/mutex.h:161:0: note: this is the location of the previous definition
This simply removes the private implementation and uses the
normal mutex_lock_killable directly.
We could do the same for the down_interruptible_killable here, but
it's better to just remove the semaphores entirely from the driver,
which also takes care of that.
Signed-off-by: Arnd Bergmann <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions