-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
libdrm 2.4.76 has been released.
This release is required for upcoming Radeon Vega GPUs.
Adam Jackson (1): configure: Explicitly check for pkg-config at the top level
Alex Xie (3): amdgpu: Free/uninit vamgr_32 in theoretically correct order amdgpu: vamgr_32 can be a struct instead of a pointer amdgpu: vamgr can be a struct instead of a pointer
Chris Wilson (3): intel: Move is_softpin to obj->kflags intel: Move 48b support to bo_gem->kflags intel: Add handle to hashtable before freeing along an error path
Christian König (1): amdgpu: stop reading CC_RB_BACKEND_DISABLE on Vega10
Emil Velikov (2): Remove unused tests/drmstat.c headers: add explicit note against local changes in the README
Eric Engestrom (2): autogen.sh: don't print old git-config values autogen.sh: run git commands in the (potentially) git dir
Huang Rui (2): amdgpu: don't read registers not present on Vega10 tests/amdgpu: fix the count number for vega10
Junwei Zhang (1): tests/amdgpu: add Polaris12 support for cs test
Leo Liu (3): tests/amdgpu: add uvd unit test support for vega10 tests/amdgpu: add vce unit test support for vega10 amdgpu_drm: add AMDGPU_HW_IP_UVD_ENC
Marek Olšák (3): amdgpu: sync amdgpu_drm.h with kernel 4.11-rc2 amdgpu: update amdgpu_drm.h for Vega10 configure.ac: bump version for release
Rob Clark (3): freedreno: fix potential use-after-free on a5xx+ freedreno: valgrind support freedreno: fix device close issues
Thomas Hindoe Paaboel Andersen (1): intel: avoid null pointer dereference
git tag: libdrm-2.4.76
http://dri.freedesktop.org/libdrm/libdrm-2.4.76.tar.bz2 MD5: 7a28eedd84459ac97017f1aa437237ac libdrm-2.4.76.tar.bz2 SHA1: dc96f064472d3ca58a7004f3219949d749219400 libdrm-2.4.76.tar.bz2 SHA256: 7cdfb83ea77def453299dd95332aa9257c9f3534ff5844f5c0ce87265c275f3a libdrm-2.4.76.tar.bz2
http://dri.freedesktop.org/libdrm/libdrm-2.4.76.tar.gz MD5: 3c01deb06d6fd5989141092b88e3d991 libdrm-2.4.76.tar.gz SHA1: 832826f2bdcfb66e59f99aed51a61ee76fb9b722 libdrm-2.4.76.tar.gz SHA256: 6e3fb50d7500acf06f7eed44d5b1d33cda26aef7f5ae6667ddcc626b435c2531 libdrm-2.4.76.tar.gz
On Wed, 29 Mar 2017, Marek Olšák maraeo@gmail.com wrote:
libdrm 2.4.76 has been released.
git tag: libdrm-2.4.76
Should the release tags be signed? For a couple of years that has been the practise until this release. Admittedly RELEASING doesn't even say anything about tagging, let alone signing the tag.
BR, Jani.
On 30 March 2017 at 07:04, Jani Nikula jani.nikula@linux.intel.com wrote:
On Wed, 29 Mar 2017, Marek Olšák maraeo@gmail.com wrote:
libdrm 2.4.76 has been released.
git tag: libdrm-2.4.76
Should the release tags be signed? For a couple of years that has been the practise until this release. Admittedly RELEASING doesn't even say anything about tagging, let alone signing the tag.
Some of these questions were answered on #dri-devel. Repeating here for posterity: Most likely Marek used an old release.sh script.
For those wondering the script does: - run make dist/distcheck to create and check the tarballs - sign the tarballs - create and sign the tag - push the tag, tarballs - create the summary template
-Emil
dri-devel@lists.freedesktop.org