diff options
author | Linus Torvalds | 2020-12-11 10:22:17 -0800 |
---|---|---|
committer | Linus Torvalds | 2020-12-11 10:22:17 -0800 |
commit | 6d47cdecaa45c88ba3858323aa54ec9aa1de1a9b (patch) | |
tree | 0416dea7956d278d44e103eed677b336443a8dc1 /security | |
parent | c1cea11227cb57f1ab0f111b3f6e8a250b85cfdb (diff) | |
parent | 263ade7166a2e589c5b605272690c155c0637dcb (diff) |
Merge tag 'v5.10-3' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio
Pull GPIO fixes from Linus Walleij:
"These are hopefully the last GPIO fixes for this cycle.
All are driver fixes except a small resource leak for pin ranges in
the gpiolib. Two are PM related, which is nice because when developers
start to find PM bugs it is usually because they have smoked out the
bugs of more severe nature.
Summary:
- Fix runtime PM balancing on the errorpath of the Arizona driver
- Fix a suspend NULL pointer reference in the dwapb driver
- Balance free:ing in gpiochip_generic_free()
- Fix runtime PM balancing on the errorpath of the zynq driver
- Fix irqdomain use-after-free in the mvebu driver
- Break an eternal loop in the spreadtrum EIC driver"
* tag 'v5.10-3' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio:
gpio: eic-sprd: break loop when getting NULL device resource
gpio: mvebu: fix potential user-after-free on probe
gpio: zynq: fix reference leak in zynq_gpio functions
gpiolib: Don't free if pin ranges are not defined
gpio: dwapb: fix NULL pointer dereference at dwapb_gpio_suspend()
gpio: arizona: disable pm_runtime in case of failure
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions