From: Russell King <rmk@arm.linux.org.uk>
To: David Airlie <airlied@linux.ie>
Cc: dri-devel@lists.freedesktop.org
Subject: [GIT PULL] Armada DRM development updates development updates
Date: Tue, 22 Dec 2015 16:37:07 +0000 [thread overview]
Message-ID: <20151222163707.GA9855@rmk-PC.arm.linux.org.uk> (raw)
David,
Please incorporate the latest Armada DRM development updates development
updates, which can be found at:
git://ftp.arm.linux.org.uk/~rmk/linux-arm.git drm-armada-devel
with SHA1 0b8ebeacf5ef43a467c7ec5400ccc1ffc3fbdfba.
These are the patches from Daniel Vetter, getting rid of struct_mutex
from the Armada DRM driver.
This will update the following files:
drivers/gpu/drm/armada/armada_crtc.c | 9 ++-------
drivers/gpu/drm/armada/armada_debugfs.c | 4 ++--
drivers/gpu/drm/armada/armada_drm.h | 3 ++-
drivers/gpu/drm/armada/armada_drv.c | 1 +
drivers/gpu/drm/armada/armada_gem.c | 29 +++++++++++++++--------------
5 files changed, 22 insertions(+), 24 deletions(-)
through these changes:
Daniel Vetter (5):
drm/armada: use unlocked gem unreferencing
drm/armada: plug leak in dumb_map_offset
drm/armada: don't grab dev->struct_mutex for in mmap offset ioctl
drm/armada: drop struct_mutex from cursor paths
drm/armada: use a private mutex to protect priv->linear
Many thanks.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-12-22 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 16:37 Russell King [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-11-22 10:37 [GIT PULL] Armada DRM development updates development updates Russell King
2015-10-14 16:32 Russell King
2015-05-28 9:35 Russell King
2015-05-09 13:31 Russell King
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=20151222163707.GA9855@rmk-PC.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
/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