From: "Marek Olšák" <maraeo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
xorg-announce-go0+a7rfsptAfugRpC6u6w@public.gmane.org,
amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: libdrm 2.4.93
Date: Tue, 31 Jul 2018 21:49:45 -0400 [thread overview]
Message-ID: <20180801014945.21840-1-maraeo@gmail.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Christian König (1):
amdgpu: make sure to set CLOEXEC on duplicated FDs
Emil Velikov (10):
xf86drm: drmGetDevice2: error out if the fd has unknown subsys
xf86drm: introduce drm_device_has_rdev() helper
xf86drm: Fold drmDevice processing into process_device() helper
xf86drm: Allocate drmDevicePtr's on stack
xf86drm: introduce a get_real_pci_path() helper
xf86drm: Add drmDevice support for virtio_gpu
tests/drmdevices: install alongside other utilities
tests/drmdevice: add a couple of printf headers
drmdevice: convert the tabbed output into a tree
drmdevice: print the correct host1x information
Jan Vesely (3):
amdgpu: Take a lock before removing devices from fd_tab hash table.
amdgpu/util_hash_table: Add helper function to count the number of entries in hash table
amdgpu: Destroy fd_hash table when the last device is removed.
José Roberto de Souza (2):
intel: Introducing Whiskey Lake platform
intel: Introducing Amber Lake platform
Kevin Strasser (1):
xf86drm: Be sure to closedir before return
Marek Olšák (3):
amdgpu: don't call add_handle_to_table for KMS BO exports
amdgpu: add amdgpu_bo_handle_type_kms_noimport
configure.ac: bump version to 2.4.93
Mariusz Ceier (1):
xf86drm: Fix error path in drmGetDevice2
Michel Dänzer (2):
Always pass O_CLOEXEC when opening DRM file descriptors
Revert "amdgpu: don't call add_handle_to_table for KMS BO exports"
Rob Clark (5):
freedreno: add user ptr to fd_ringbuffer
freedreno: add fd_ringbuffer_new_object()
freedreno: small cleanup
freedreno: slight reordering
freedreno/msm: "stateobj" support
git tag: libdrm-2.4.93
https://dri.freedesktop.org/libdrm/libdrm-2.4.93.tar.bz2
MD5: 0ba45ad1551b2c1b6df0797a3e65f827 libdrm-2.4.93.tar.bz2
SHA1: 550ba4bb50236fc2e9138cbeadcb4942ce09410e libdrm-2.4.93.tar.bz2
SHA256: 6e84d1dc9548a76f20b59a85cf80a0b230cd8196084f5243469d9e65354fcd3c libdrm-2.4.93.tar.bz2
SHA512: ba4221e8d6a3a9872fb6d30a0ea391e30ea0e17f249c66f067bed9c2161ed1ad8083959cb2c212834c6566c3e025f4daae31e9533d77aae19bbbbb9de6c2ab3d libdrm-2.4.93.tar.bz2
PGP: https://dri.freedesktop.org/libdrm/libdrm-2.4.93.tar.bz2.sig
https://dri.freedesktop.org/libdrm/libdrm-2.4.93.tar.gz
MD5: 2df4729a0e9829d77a7a0a7a8dda2f66 libdrm-2.4.93.tar.gz
SHA1: 3947aeecb6ecc271c657638f97e8d21753cedf6e libdrm-2.4.93.tar.gz
SHA256: bc67b2503106155c239c4e455b6718ef1b31675ea51f544c785c0e3295712861 libdrm-2.4.93.tar.gz
SHA512: 3ca334ee46fe50103e146463d2dab85c7a075559192a85bfe73ca2f80cb8a8847b19775b1a16271b537656e9d7a48f0e209ea7227a3e1ebd9fa3a5caf38047f2 libdrm-2.4.93.tar.gz
PGP: https://dri.freedesktop.org/libdrm/libdrm-2.4.93.tar.gz.sig
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCgAdFiEEzUfFNBo3XzO+97r6/dFdWs7w8rEFAlthEUoACgkQ/dFdWs7w
8rGVWAf/bV1GNvp0Aakm95UhIHC61CvZk7PxnSADd3SlZC6BE9K5WNK2jumtXQln
o1EmXc1WS2b02jPQVX4+qv/F8gxVlHdKDbi52Rk1RnK0ii7gP2oGf+4q0EUrdwoq
HYE6XHppUFgBVRBXTa0vCqVBo/KYWRgPlSPNlEsxigPzRk00Qt0vWEjQiN8vTmH2
+YReSIvOQxmZ/CSU8/+JaV395S+7nc59HG18xHvjcC6F4AelWBFdAA+P782yTeJ5
nr952bkr7+Z5/n/XWUkzdTr11YSHev5N24JYxopvXgbmDr+Dz/hdIYyy8MGJSKp0
q+2RVWP6WlNlXh2KUvwPM9SZydxkDA==
=DmZ7
-----END PGP SIGNATURE-----
_______________________________________________
xorg-announce mailing list
xorg-announce@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-announce
reply other threads:[~2018-08-01 1:49 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=20180801014945.21840-1-maraeo@gmail.com \
--to=maraeo-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=xorg-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=xorg-announce-go0+a7rfsptAfugRpC6u6w@public.gmane.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