All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marek Olšák" <maraeo@gmail.com>
To: dri-devel@lists.freedesktop.org, xorg-announce@lists.x.org
Subject: [ANNOUNCE] libdrm 2.4.77
Date: Tue,  4 Apr 2017 11:56:53 +0200	[thread overview]
Message-ID: <1491299813-21262-1-git-send-email-maraeo@gmail.com> (raw)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Bernd Kuhls (1):
      tests/etnaviv: link against libdrm

Christian Gmeiner (1):
      etnaviv: remove struct etna_specs

Emil Velikov (2):
      amdgpu: add amdgpu_bo_va_op_raw to the symbol check
      configure.ac: bring back pthread-stubs check

Erik Faye-Lund (1):
      tegra: update symbol-check

Junwei Zhang (1):
      amdgpu: add REPLACE and CLEAR checking for VA op (v2)

Marek Olšák (1):
      configure.ac: bump the version to 2.4.77

Nicolai Hähnle (3):
      amdgpu: add amdgpu_bo_va_op_raw
      headers: sync amdgpu_drm.h from airlied/drm-next
      headers: the uint*_t vs. __u* discrepancy in amdgpu_drm is fixed

Rob Herring (2):
      Android: fix building of modetest and proptest
      Android: disable pointer-arith and enum-conversion

Seung-Woo Kim (5):
      exynos: fix type-punned pointer build warning
      exynos/fimg2d: remove unused-function build warning
      tests/exynos: remove unused-function build warning
      tests/exynos: fix invalid code of error path in g2d test
      xf86drm: remove memory leaks in drmGetBusid/drmGetReservedContextList

git tag: libdrm-2.4.77

https://dri.freedesktop.org/libdrm/libdrm-2.4.77.tar.bz2
MD5:  f03e095b591d62b5b5fc9ec79efebf64  libdrm-2.4.77.tar.bz2
SHA1: 705709656512c5d2759ecfe9a71c92a64ffe9f51  libdrm-2.4.77.tar.bz2
SHA256: e8d5e2ca3a42a4d02b4df97fde45a12eeeb34c158008361026f82c8bf6fb3b6d  libdrm-2.4.77.tar.bz2
SHA512: df313bdd9186efdb0e60acdd55e0d5dba402b19011bc3899d56efb4d065f67b6e8c44108fbd8fd258120d4b5c1cc53090beaab732c763bf52f8b352d3c30d101  libdrm-2.4.77.tar.bz2
PGP:  https://dri.freedesktop.org/libdrm/libdrm-2.4.77.tar.bz2.sig

https://dri.freedesktop.org/libdrm/libdrm-2.4.77.tar.gz
MD5:  c6cb224b6364f8c3378dd85fb2091f9c  libdrm-2.4.77.tar.gz
SHA1: 1086f487f1b76eab8ce650394677146a578e814c  libdrm-2.4.77.tar.gz
SHA256: 09b7b71b0396534d7750745c161e4f8cb782d4a67739f710e1418ef5f083a09d  libdrm-2.4.77.tar.gz
SHA512: bdb5e36b1cb6734180d5fd231dc59056a82ad86651f69de84d2ba52b4ef43e8b1990c41932c60b8490813747880a721bdb019204b7f3a94d6ae62a114109c8e2  libdrm-2.4.77.tar.gz
PGP:  https://dri.freedesktop.org/libdrm/libdrm-2.4.77.tar.gz.sig

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJY422bAAoJEP3RXVrO8PKxCREH/jrTftAubWZQ0irlunh1cv7h
znp9Wx1JWIWW36LYiC7E+vEksCCutxdoO6geYi3g/KFbcHg18sU611aKJZukylY4
wh+UhralkNjCPDi3uv33DOr8iSQkn15xatH/WjE2oGL9JTM1mGaAmU/XglXA3cGZ
/o83f/R1ZhwFH99fTMnbenFWofaHTkwKNxpftWUj6UOeRCOYQQALKygOLG9hr9tB
s+ooZREdYw1hRl/X61b496+Hv8jJ9SUo8e+HBr5ibV9yEb2boZzz5kXsp6KnV2ry
MI9lZHbqyNd1NFYKIrYnrpixsqkC3N/vtfdK5HOloKE6WwBKfBWxLGXVhpnjjfA=
=9anU
-----END PGP SIGNATURE-----
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

                 reply	other threads:[~2017-04-04  9:57 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=1491299813-21262-1-git-send-email-maraeo@gmail.com \
    --to=maraeo@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.