summaryrefslogtreecommitdiffstats
path: root/tools/perf/builtin-script.c
diff options
context:
space:
mode:
authorGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-01-31 08:57:51 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-01-31 08:57:51 +0100
commitc7b0c3bbe4c2c28df54f7161d6ecb2b555d25a35 (patch)
treeff009992bad94da8070c14fb85c7797c5f55a483 /tools/perf/builtin-script.c
parentc418fd6c01fbc5516a2cd1eaf1df1ec86869028a (diff)
parenta53469a68eb886e84dd8b69a1458a623d3591793 (diff)
downloadlinux-c7b0c3bbe4c2c28df54f7161d6ecb2b555d25a35.tar.gz
linux-c7b0c3bbe4c2c28df54f7161d6ecb2b555d25a35.tar.bz2
linux-c7b0c3bbe4c2c28df54f7161d6ecb2b555d25a35.zip
Merge tag 'fixes-for-v5.0-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb into usb-linus
Felipe writes: usb: fixes for v5.0-rc4 Dwc3 got a fix for cases when gadget driver queue an OUT request of length 0; this is a case that has been overlooked for quite some time now. Exynos' dwc3 glue layer got a fix on the error path for those cases where clk_prepare_enable() fails. TI's AM335x PHY driver got a fix for a race condition during probe. This race happened because driver was powering off the PHY only after adding the PHY handle to the framework. The result is that we could fall into a situation where user of the PHY (MUSB) could call phy_init() before phy driver's probe() called phy_poweroff() which would result in a powered off PHY after phy_init() was called. The old net2272 driver got a fix for an erroneous use of bitwise negation. * tag 'fixes-for-v5.0-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb: usb: phy: am335x: fix race condition in _probe usb: dwc3: exynos: Fix error handling of clk_prepare_enable usb: phy: fix link errors usb: gadget: udc: net2272: Fix bitwise and boolean operations usb: dwc3: gadget: Handle 0 xfer length for OUT EP
Diffstat (limited to 'tools/perf/builtin-script.c')
0 files changed, 0 insertions, 0 deletions