summaryrefslogtreecommitdiff
path: root/sound/firewire/fireworks
diff options
context:
space:
mode:
authorRob Clark <robdclark@gmail.com>2017-01-12 17:41:44 -0500
committerRob Clark <robdclark@gmail.com>2017-01-13 10:23:00 -0500
commitde85d2b35ac74f6be769573d4a8708c823219900 (patch)
tree5b32e7cb9254da81a1babad707e8ef76d56f4d43 /sound/firewire/fireworks
parentc57a94ffd0105d58ab104fe383148c5eda5aa033 (diff)
drm/msm: fix potential null ptr issue in non-iommu case
Fixes: 9cb07b099fb ("drm/msm: support multiple address spaces") Reported-by: Riku Voipio <riku.voipio@linaro.org> Signed-off-by: Rob Clark <robdclark@gmail.com>
Diffstat (limited to 'sound/firewire/fireworks')
0 files changed, 0 insertions, 0 deletions
hich is there for a long time) - without these patches data loss can occur on power failure even though user called fsync(2). The other three patches change locking of DAX faults so that ->iomap_begin() is called in a more relaxed locking context and we are safe to start a transaction there for ext4" These have received a build success notification from the kbuild robot, and pass the latest libnvdimm unit tests. There have not been any -next releases since -rc1, so they have not appeared there" * 'libnvdimm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm: ext4: Simplify DAX fault path dax: Call ->iomap_begin without entry lock during dax fault dax: Finish fault completely when loading holes dax: Avoid page invalidation races and unnecessary radix tree traversals mm: Invalidate DAX radix tree entries only if appropriate ext2: Return BH_New buffers for zeroed blocks
Diffstat (limited to 'sound/atmel')