aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2016-11-16 16:39:05 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2016-11-16 18:30:46 +0100
commitb826d73b3024485677163253b59ef9bd187ff765 (patch)
tree9988b08f99263000cfdc0a13d6d2875fca1fa046 /tools/perf/scripts/python/call-graph-from-postgresql.py
parentstaging: wilc1000: simplify vif[i]->ndev accesses (diff)
downloadwireguard-linux-b826d73b3024485677163253b59ef9bd187ff765.tar.xz
wireguard-linux-b826d73b3024485677163253b59ef9bd187ff765.zip
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 <arnd@arndb.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions