From: Alex Deucher <alexdeucher@gmail.com>
To: dri-devel@lists.freedesktop.org, airlied@gmail.com
Cc: Alex Deucher <alexander.deucher@amd.com>
Subject: [pull] radeon drm-fixes-3.18
Date: Wed, 12 Nov 2014 11:27:45 -0500 [thread overview]
Message-ID: <1415809665-28738-1-git-send-email-alexander.deucher@amd.com> (raw)
Hi Dave,
Just your atom scratch buffer locking fix.
The following changes since commit 03dca708521d30153fc5c7e2ff136f780a7372c9:
Merge tag 'drm-intel-fixes-2014-11-07' of git://anongit.freedesktop.org/drm-intel into drm-fixes (2014-11-10 10:05:37 +1000)
are available in the git repository at:
git://people.freedesktop.org/~agd5f/linux drm-fixes-3.18
for you to fetch changes up to 1c9498425453bb65ef339a57705c5ef59fe1541d:
drm/radeon: add locking around atombios scratch space usage (2014-11-11 17:22:26 -0500)
----------------------------------------------------------------
Dave Airlie (1):
drm/radeon: add locking around atombios scratch space usage
drivers/gpu/drm/radeon/atom.c | 11 ++++++++++-
drivers/gpu/drm/radeon/atom.h | 2 ++
drivers/gpu/drm/radeon/atombios_dp.c | 4 +++-
drivers/gpu/drm/radeon/atombios_i2c.c | 4 +++-
drivers/gpu/drm/radeon/radeon_device.c | 1 +
5 files changed, 19 insertions(+), 3 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2014-11-12 16:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 16:27 Alex Deucher [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-02 20:57 [pull] radeon drm-fixes-3.18 Alex Deucher
2014-11-20 17:21 Alex Deucher
2014-11-06 22:44 Alex Deucher
2014-10-30 19:58 Alex Deucher
2014-10-16 22:43 Alex Deucher
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=1415809665-28738-1-git-send-email-alexander.deucher@amd.com \
--to=alexdeucher@gmail.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--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