From: Daniel Stone <daniels@collabora.com>
To: xorg-announce <xorg-announce@lists.x.org>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: [ANNOUNCE] libdrm 2.4.83
Date: Thu, 24 Aug 2017 12:51:21 +0100 [thread overview]
Message-ID: <1503575481.18775.2.camel@collabora.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Boyuan Zhang (1):
tests/amdgpu: add uvd encode unit tests
Chih-Wei Huang (2):
android: add rules to build amdgpu.ids
android: amdgpu: fix build break
Daniel Stone (1):
configure.ac: Bump version to 2.4.83
Emil Velikov (1):
xf86drm: continue with next device if drmProcessUsbDevice fails
Eric Engestrom (4):
radeon: add fallthrough annotation
freedreno: remove dead error path
freedreno/msm: remove dead error path
freedreno: prevent deadlock in error path
Flora Cui (1):
test/amdgpu: fix test failure for SI
Gurchetan Singh (1):
xf86drm: continue after drmProcessPlatformDevice failure
Hawking Zhang (2):
tests/amdgpu: bypass UVD CS tests on raven
tests/amdgpu: bypass VCE tests on raven
Jan Vesely (2):
amdgpu: Add FX-9800P Bristol Ridge iGPU id
drmsltest: Check expected neighbours
Jason Ekstrand (1):
drm: Pull new modifier uapi into drm_fourcc and drm_mode
Monk Liu (3):
amdgpu: fix missing mutex unlock before return
amdgpu: fix race issue between two bo functions(v2)
amdgpu: merge and cleanup amdgpu_bo_free
Philipp Zabel (1):
etnaviv: fix etna_bo_from_name
git tag: libdrm-2.4.83
https://dri.freedesktop.org/libdrm/libdrm-2.4.83.tar.bz2
MD5: 23800953ed7564988872e1e8c61fde31 libdrm-2.4.83.tar.bz2
SHA1: f78d392684d6e482e8c0a85d355619ac64c4ad6a libdrm-2.4.83.tar.bz2
SHA256: 03a52669da60ead62548a35bc430aafb6c2d8dd21ec9dba3a90f96eff5fe36d6 libdrm-2.4.83.tar.bz2
SHA512: 8f894ff61939bca03ac857506a84bbbcbe2367e60c91a0f2388bfce5ae81e12ba2f96fe1c962416cf9e2d25ef04b98b5437c7015497789561311a72607b3bfcb libdrm-2.4.83.tar.bz2
PGP: https://dri.freedesktop.org/libdrm/libdrm-2.4.83.tar.bz2.sig
https://dri.freedesktop.org/libdrm/libdrm-2.4.83.tar.gz
MD5: d6debc2bde08a0bfff61fe848d760f6d libdrm-2.4.83.tar.gz
SHA1: b80228d235805e46f0d8e62ab1f7231ebd2fd67e libdrm-2.4.83.tar.gz
SHA256: 2ff5f626a14ec5bd680f7769cac9a8eb1e40c36cf5ca554d2c4e5d91bab3d81d libdrm-2.4.83.tar.gz
SHA512: 0ca90a30808cafdf7178b482e5121968bcaac9a48b4f4f969a88c3584043a24b9734ea2b747b46fc72053df15fc1f81e658176ad637a72a0c935450753ab6a7a libdrm-2.4.83.tar.gz
PGP: https://dri.freedesktop.org/libdrm/libdrm-2.4.83.tar.gz.sig
-----BEGIN PGP SIGNATURE-----
iQIcBAEBAgAGBQJZnr1BAAoJEMzE8H+sZB7/U0kP/2YTIzOlwOW0mZZ1H0KbBST3
gvg5ywaJDHnUp0jHO+qM589La2hDaLRSUvRvwtjU8phqNcJkl5RJxyy6PhCGQ0OY
auJv5j82gQArrTyIsMeEZEhXjq9SmB5ntQk/HmV60Ct3xH6y88pDYjvPqZ31Q0CM
kvRKtmV80KTp1uDVo8x+FifdeZtL7+SBllgYgTk46YCZj1NtFe4w0FsPn1OQjMMy
52JIVxBOvR2Jk5Y8AlOdWTRTdJbku080eaumGuHKvo7ESy98GJmBHdvpRZVDWyle
9FVxz10TXPUmUMxubysv3o4oiOfZOlkvo/wRPozcQ1+ph3grF7c+GNgXF8bq9Qd2
meTWJMBEq/sQ+jvEZlJt/9cDpJhg/tC0O5X65PErzECEoY5DJkdsRQ2moPWjS4C/
miMGrK9ufqZdcXG0OxKW5wyIdus6gYV3RJXlwveoKkjUOvdqxcepJiPWlxL4sDJJ
gDfs0qs2Pi1V/XNCFMeyBqNxFTt9c5zJbLkz83e6cDG8CeKecDaK9Dy/v0COmKfe
K/r8OoPVr+xY0dFY63Jua3Xa146vL57+T/xNjEJgtndCODvR4MOfkzN7u40wuG8q
U+9wIQAyoVkg2HTcszt4Ynz/TEFWvotHo0gC/srQuOaek6xS9zJGYhv87kqNRVzk
uTjAC5zDXjHp6ZNtRmII
=W/DQ
-----END PGP SIGNATURE-----
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
reply other threads:[~2017-08-24 11:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1503575481.18775.2.camel@collabora.com \
--to=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=xorg-announce@lists.x.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