summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-sqlite.py
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2025-01-28 02:45:29 +0300
committerLinus Torvalds <torvalds@linux-foundation.org>2025-01-28 02:45:29 +0300
commit078eac2b5ba3532ad3ded7c4aa10df8712722c50 (patch)
tree1f598a3d353c70fcbcff0a8c95df25044385659f /tools/perf/scripts/python/export-to-sqlite.py
parentf28f4890454cc97c18d31ab4686957857cc862b5 (diff)
parentda6b353786997c0ffa67127355ad1d54ed3324c2 (diff)
downloadlinux-078eac2b5ba3532ad3ded7c4aa10df8712722c50.tar.xz
Merge tag 'pwm/for-6.14-rc1-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux
Pull pwm fixes from Uwe Kleine-König: "Two fixes. Conor Dooley found and fixed a problem in the pwm-microchip-core driver that existed since the driver's birth in v6.5-rc1. It's about a corner case that only happens if two pwm devices of the same chip are set to the same long period. The other problem is about the new pwm API that currently is only supported by two hardware drivers. The fix prevents a NULL pointer exception if one of the new functions is called for a pwm device with a driver that only provides the old callbacks" * tag 'pwm/for-6.14-rc1-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux: pwm: Ensure callbacks exist before calling them pwm: microchip-core: fix incorrect comparison with max period
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions