summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/check-perf-trace.py
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2025-02-21 19:59:27 +0300
committerLinus Torvalds <torvalds@linux-foundation.org>2025-02-21 19:59:27 +0300
commit534a2c6217f21a66e72d246417e0cae25c5a3d62 (patch)
tree8100f6353156f49785501114d67708c33499985a /tools/perf/scripts/python/check-perf-trace.py
parent334426094588f8179fe175a09ecc887ff0c75758 (diff)
parent96fa9ec477ff60bed87e1441fd43e003179f3253 (diff)
downloadlinux-534a2c6217f21a66e72d246417e0cae25c5a3d62.tar.xz
Merge tag 'gpio-fixes-for-v6.14-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux
Pull gpio fixes from Bartosz Golaszewski: "There are two fixes for GPIO core: one adds missing retval checks to older code, while the second adds SRCU synchronization to legs in code that were missed during the big rework a few cycles back. There's also one small driver fix: - check the return value of the get_direction() callback in struct gpio_chip - protect the multi-line get/set legs in GPIO core with SRCU - fix a race condition in gpio-vf610" * tag 'gpio-fixes-for-v6.14-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux: gpiolib: don't bail out if get_direction() fails in gpiochip_add_data() gpiolib: protect gpio_chip with SRCU in array_info paths in multi get/set gpio: vf610: add locking to gpio direction functions gpiolib: check the return value of gpio_chip::get_direction()
Diffstat (limited to 'tools/perf/scripts/python/check-perf-trace.py')
0 files changed, 0 insertions, 0 deletions