summaryrefslogtreecommitdiff
path: root/drivers/leds/led-core.c
diff options
context:
space:
mode:
authorDave Airlie <airlied@redhat.com>2021-04-18 02:26:54 +0300
committerDave Airlie <airlied@redhat.com>2021-04-18 02:27:00 +0300
commit796b556cbfdbe0d65b9793e63653ad24f9fa033c (patch)
treecfdc57e0d8343f65a59d31eef1ceb0544beda18e /drivers/leds/led-core.c
parent4d2e1288372ccc5ac60290bc10cace49c9bfa6d0 (diff)
parent2ef4fb92363c44e8a6f93fd0877b6a7dee6f874d (diff)
downloadlinux-796b556cbfdbe0d65b9793e63653ad24f9fa033c.tar.xz
Merge tag 'vmwgfx-fixes-2021-04-14' of gitlab.freedesktop.org:zack/vmwgfx into drm-fixes
vmwgfx fixes for regressions in 5.12 Here's a set of 3 patches fixing ugly regressions in the vmwgfx driver. We broke lock initialization code and ended up using spinlocks before initialization breaking lockdep. Also there was a bit of a fallout from drm changes which made the core validate that unreferenced buffers have been unpinned. vmwgfx pinning code predates a lot of the core drm and wasn't written to account for those semantics. Fortunately changes required to fix it are not too intrusive. The changes have been validated by our internal ci. Signed-off-by: Zack Rusin <zackr@vmware.com> Signed-off-by: Dave Airlie <airlied@redhat.com> From: Zack Rusin <zackr@vmware.com> Link: https://patchwork.freedesktop.org/patch/msgid/f7add0a2-162e-3bd2-b1be-344a94f2acbf@vmware.com
Diffstat (limited to 'drivers/leds/led-core.c')
0 files changed, 0 insertions, 0 deletions