summaryrefslogtreecommitdiff
path: root/drivers/memstick
diff options
context:
space:
mode:
authorDave Airlie <airlied@redhat.com>2024-01-27 04:04:34 +1000
committerDave Airlie <airlied@redhat.com>2024-01-27 04:04:34 +1000
commit4d7acc8f48bcf27d0dc068f02e55c77e840b9110 (patch)
tree359f76cc3a1256f988bb886cee53aba14ea39938 /drivers/memstick
parent9c4a1126ad9ce6699cc6ad2ca7c590cd1203c70f (diff)
downloadlinux-4d7acc8f48bcf27d0dc068f02e55c77e840b9110.tar.gz
linux-4d7acc8f48bcf27d0dc068f02e55c77e840b9110.tar.bz2
linux-4d7acc8f48bcf27d0dc068f02e55c77e840b9110.zip
Revert "nouveau: push event block/allowing out of the fence context"
This reverts commit eacabb5462717a52fccbbbba458365a4f5e61f35. This commit causes some regressions in desktop usage, this will reintroduce the original deadlock in DRI_PRIME situations, I've got an idea to fix it by offloading to a workqueue in a different spot, however this code has a race condition where we sometimes miss interrupts so I'd like to fix that as well. Cc: stable@vger.kernel.org Signed-off-by: Dave Airlie <airlied@redhat.com>
Diffstat (limited to 'drivers/memstick')
0 files changed, 0 insertions, 0 deletions