From: Kenneth Graunke <kenneth@whitecape.org>
To: xorg-announce@lists.freedesktop.org,
DRI Devel <dri-devel@lists.freedesktop.org>
Subject: [ANNOUNCE] libdrm 2.4.52
Date: Mon, 20 Jan 2014 15:04:18 -0800 [thread overview]
Message-ID: <52DDAB72.9090509@whitecape.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ben Widawsky (3):
intel: squash unused variable 'bo_gem'
intel: Handle malloc fails in context create
intel: Merge latest i915_drm.h
Eric Anholt (2):
drm: Initialize or valgrind-clear modesetting ioctl arguments.
intel: Track whether a buffer is idle to avoid trips to the kernel.
Hyungwon Hwang (1):
tests/kmstest: support exynos
Keith Packard (1):
Mark debug_print with __attribute__ ((format(__printf__, 1, 0)))
Kenneth Graunke (2):
intel: Create a new drm_intel_bo offset64 field.
Bump the version to 2.4.52
Rob Clark (1):
freedreno: add fd_device_new_dup()
Vincent ABRIOU (1):
modetest: add the possibility to select the refresh frequency for a mode
git tag: libdrm-2.4.52
http://dri.freedesktop.org/libdrm/libdrm-2.4.52.tar.bz2
MD5: 01b75624a5da3a7543923e54c3547a24 libdrm-2.4.52.tar.bz2
SHA1: 7be6767efd0988c76c984fcdd1c8b712bcb9aea5 libdrm-2.4.52.tar.bz2
SHA256: fa693c2f1f61befcefbdcc396673e38481110bac9db610afa4b8afb2be0218c1 libdrm-2.4.52.tar.bz2
http://dri.freedesktop.org/libdrm/libdrm-2.4.52.tar.gz
MD5: cb3547ccb435be6d80df68840da6b2ee libdrm-2.4.52.tar.gz
SHA1: 356719ddee5d24b02106824ff69774e1f540ac9f libdrm-2.4.52.tar.gz
SHA256: 8430fdc2edf11bce8932b6dbbe1cd128056e36865b13c7633a3298d7c42e7d08 libdrm-2.4.52.tar.gz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJS3atyAAoJEFtb2gcdScw4duYP/R+y23oK09C5NeCz3DTLyIQi
n7LHnZ37xDZ2A/g+FORQNyglPMPZ3Ey6M8NkpJ0NRS8tN8W90ezVVubwMEUF8doW
wtEw9ehSMXzhBu6R0Ervy1EjP7GygbmsWL6Pc+JXE7aNQ+l9Yi/7+zYZgb1KPYRv
znq8VEi6EC9kLIEBrTnE6x/WBHQA/fdvMXAeww+y5ru+7Inlc4yxtFS/k0euBJox
ytD1NbVLtPzafjgiD7XElPeiXchPoUYEZ5FffQv3HUo2OYKhydg13A7GeUyTRW5D
J4uPSnGoAEF+IDnYL37tzeDVMjFZX0JigwAGFVNltkvuTWVsFbPO31PEyu8JbibJ
mvKTsRdfKQzkVC9NEuE26e96M1VdTQsmbxApc9eNp5DaNxfsahq0bWF7vnzQ0Qhy
qtRkRvd9WfVszV9bg53wvIos3u6DIugZ+dqIeSizMRDx5LXVPYmffChN38BhREvK
elsdL9v0wgb0U17mS52IesR1CJl2NdnAREkaT9iDKeVfySmWUZGumdX75q12eEUo
I+9yH0/79mq+mQ0j0FrUZLSsrwIpxLYsJRcRwOEVLKwuppL8r3C2aTDvE8zNJptA
Izh5rxVXptCjfnLnzEo+V5az+RU8Ufp0MSj7HSiLxxg/Fd/dER7RjjyETUDlHJW5
JV65i5mwH4J6T85PRIEO
=FaHh
-----END PGP SIGNATURE-----
reply other threads:[~2014-01-20 23:00 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=52DDAB72.9090509@whitecape.org \
--to=kenneth@whitecape.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=xorg-announce@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