From: Tobias Geerinckx-Rice via Guix-patches <guix-patches@gnu.org>
To: 36814-done@debbugs.gnu.org
Subject: bug#36814: [PATCH 0/2] Add VA-API Intel back-end and utilities
Date: Sat, 27 Jul 2019 23:29:35 +0200 [thread overview]
Message-ID: <87d0hvgo8w.fsf@nckx> (raw)
In-Reply-To: <871rydiifr.fsf@nckx>
[-- Attachment #1: Type: text/plain, Size: 312 bytes --]
Tobias Geerinckx-Rice via Guix-patches 写道：
> Guix,
>
> The following patches add the VA-API back end for Intel GEN
> chips as
> well as libva-utils (which provides vainfo amongst many other
> things).
Pushed atop master as 3563220e1e46b8a1b9af1e3a4c6cb3f9560c2460 &c.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2019-07-27 21:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 3:27 [bug#36814] [PATCH 0/2] Add VA-API Intel back-end and utilities Tobias Geerinckx-Rice via Guix-patches
2019-07-26 3:30 ` [bug#36814] [PATCH 1/2] gnu: Add intel-vaapi-driver Tobias Geerinckx-Rice via Guix-patches
2019-07-26 3:30 ` [bug#36814] [PATCH 2/2] gnu: Add libva-utils Tobias Geerinckx-Rice via Guix-patches
2019-07-27 18:37 ` Marius Bakke
2019-07-27 18:35 ` [bug#36814] [PATCH 1/2] gnu: Add intel-vaapi-driver Marius Bakke
2019-07-27 19:00 ` Tobias Geerinckx-Rice via Guix-patches
2019-07-26 8:17 ` [bug#36814] [PATCH 0/2] Add VA-API Intel back-end and utilities Tobias Geerinckx-Rice via Guix-patches
2019-07-26 8:56 ` Jelle Licht
2019-07-26 17:58 ` Tobias Geerinckx-Rice via Guix-patches
2019-07-26 18:40 ` [bug#36814] [BONUS PATCH 3/2] gnu: intel-vaapi-driver: Provide LIBVA_DRIVERS_PATH Tobias Geerinckx-Rice via Guix-patches
2019-07-27 18:26 ` Marius Bakke
2019-07-27 18:50 ` Tobias Geerinckx-Rice via Guix-patches
2019-07-27 19:08 ` Tobias Geerinckx-Rice via Guix-patches
2019-07-27 19:16 ` Marius Bakke
2019-07-27 19:13 ` Marius Bakke
2019-07-27 21:29 ` Tobias Geerinckx-Rice via Guix-patches [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0hvgo8w.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=36814-done@debbugs.gnu.org \
--cc=me@tobias.gr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).