From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Dave Airlie <airlied@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
dri-devel <dri-devel@lists.freedesktop.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: -next trees and my time this cycle
Date: Fri, 11 Dec 2015 10:02:45 +0000 [thread overview]
Message-ID: <20151211100245.GP8644@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAPM=9tydRybNFv0bUxmvfcapkF-iHC-n2r5mBxtUxOr=vBdd8g@mail.gmail.com>
On Fri, Dec 11, 2015 at 04:58:08PM +1000, Dave Airlie wrote:
> I've seen etnaviv, rockchip(?), vc4 gpu api, can I get plans for if
> people would like these in now, also anything I've missed on the list.
I would definitely like to see etnaviv make it in for the next merge
window, but that depends on it being reviewed, and I haven't seen
anything from DRM people yet.
I've queued up some of the TDA998x and Armada DRM changes (3 and 5
patches respectively) which I'll send you shortly if they haven't
already been merged via some other route.
--
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-12-11 10:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 6:58 -next trees and my time this cycle Dave Airlie
2015-12-11 7:13 ` Inki Dae
2015-12-11 10:02 ` Russell King - ARM Linux [this message]
2015-12-11 16:15 ` Daniel Vetter
2015-12-11 17:36 ` Russell King - ARM Linux
2015-12-12 9:42 ` Lucas Stach
2015-12-11 15:14 ` Liviu Dudau
2015-12-12 19:09 ` Linus Torvalds
2015-12-15 2:56 ` Dave Airlie
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=20151211100245.GP8644@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=torvalds@linux-foundation.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