From: Dave Airlie <airlied@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Zack Rusin <zackr@vmware.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [git pull] drm/vmwgfx fixes for 5.12-rc8
Date: Sun, 18 Apr 2021 09:48:56 +1000 [thread overview]
Message-ID: <CAPM=9tzVDp7PB0Rv8+Lmi4Ervp8QRio6phvRy_H-oFUHe3phSA@mail.gmail.com> (raw)
Hi Linus,
Back from holidays and this was in the cracks (Zack forgot to cc
Daniel/lists), I've just piled it onto drm fixes.
It contains two regression fixes for vmwgfx, one due to a refactor
which meant locks were being used before initialisation, and the other
in fixing up some warnings from the core when destroying pinned
buffers.
Dave.
drm-fixes-2021-04-18:
drm/vmwgfx fixes for 5.12-rc7
vmwgfx:
- fixed unpinning before destruction
- lockdep init reordering
The following changes since commit 4d2e1288372ccc5ac60290bc10cace49c9bfa6d0:
Merge tag 'drm-intel-fixes-2021-04-15' of
git://anongit.freedesktop.org/drm/drm-intel into drm-fixes (2021-04-15
15:24:17 +0200)
are available in the Git repository at:
git://anongit.freedesktop.org/drm/drm tags/drm-fixes-2021-04-18
for you to fetch changes up to 796b556cbfdbe0d65b9793e63653ad24f9fa033c:
Merge tag 'vmwgfx-fixes-2021-04-14' of
gitlab.freedesktop.org:zack/vmwgfx into drm-fixes (2021-04-18 09:27:00
+1000)
----------------------------------------------------------------
drm/vmwgfx fixes for 5.12-rc7
vmwgfx:
- fixed unpinning before destruction
- lockdep init reordering
----------------------------------------------------------------
Dave Airlie (1):
Merge tag 'vmwgfx-fixes-2021-04-14' of
gitlab.freedesktop.org:zack/vmwgfx into drm-fixes
Zack Rusin (3):
drm/vmwgfx: Make sure we unpin no longer needed buffers
drm/vmwgfx: Fix the lockdep breakage
drm/vmwgfx: Make sure bo's are unpinned before putting them back
drivers/gpu/drm/vmwgfx/vmwgfx_cotable.c | 4 ++++
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 17 ++++++++---------
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h | 5 +----
drivers/gpu/drm/vmwgfx/vmwgfx_mob.c | 14 ++++++++++++++
4 files changed, 27 insertions(+), 13 deletions(-)
next reply other threads:[~2021-04-17 23:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-17 23:48 Dave Airlie [this message]
2021-04-18 3:29 ` [git pull] drm/vmwgfx fixes for 5.12-rc8 pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPM=9tzVDp7PB0Rv8+Lmi4Ervp8QRio6phvRy_H-oFUHe3phSA@mail.gmail.com' \
--to=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=zackr@vmware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).