summaryrefslogtreecommitdiffstats
path: root/sound
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2016-11-18 08:47:47 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2016-11-18 08:47:47 -0800
commitbd2bc2b8e63f872f8aa0f3536a40ffce6e1840bb (patch)
tree281452c6a7e19dba44bf4c4e688b44624b4a6bff /sound
parent12b70ec0d3a6eb2696f3c091af6ecac31d2f8e66 (diff)
parentf9c22ec6c1c511285dc539b83aabdabdb6baf245 (diff)
downloadlinux-bd2bc2b8e63f872f8aa0f3536a40ffce6e1840bb.tar.bz2
Merge tag 'gpio-v4.9-4' 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 v4.9. The most important is that it fixes the UML randconfig builds that have been nagging me for some time and me being confused about where the problem was really sitting, now this fix give this nice feeling that everything is solid and builds fine. Summary: - Finally, after being puzzled by a bunch of recurrent UML build failures on randconfigs from the build robot, Keno Fischer nailed it: GPIO_DEVRES is optional and depends on HAS_IOMEM even though many users just unconditionally rely on it to be available. And it *should* be available: garbage collection is nice for this and it *certainly* has nothing to do with having IOMEM. So we got rid of it, and now the UML builds should JustWork(TM). - Do not call .get_direction() on sleeping GPIO chips on the fastpath when locking GPIOs for interrupts: it is done from atomic context, no way. - Some driver fixes" * tag 'gpio-v4.9-4' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio: gpio: Remove GPIO_DEVRES option gpio: tc3589x: fix up .get_direction() gpio: do not double-check direction on sleeping chips gpio: pca953x: Move memcpy into mutex lock for set multiple gpio: pca953x: Fix corruption of other gpios in set_multiple.
Diffstat (limited to 'sound')
0 files changed, 0 insertions, 0 deletions