From: Inki Dae <inki.dae@samsung.com>
To: Dave Airlie <airlied@gmail.com>,
dri-devel <dri-devel@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Russell King <rmk+kernel@arm.linux.org.uk>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: -next trees and my time this cycle
Date: Fri, 11 Dec 2015 16:13:29 +0900 [thread overview]
Message-ID: <566A7799.1080604@samsung.com> (raw)
In-Reply-To: <CAPM=9tydRybNFv0bUxmvfcapkF-iHC-n2r5mBxtUxOr=vBdd8g@mail.gmail.com>
Hi Dave,
2015년 12월 11일 15:58에 Dave Airlie 이(가) 쓴 글:
> Hey all,
>
> Hopefully all my sub-maintainers are awake and reading this.
>
> So since Xmas is coming up and I've got an impending new arrival, I'm
> betting this merge window might get a bit haphazard. So I'd like
> people to start telling me now via git pull's what they'd like to get
> in.
>
> 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.
> Other ARM maintainers (especially exynos) please try and get pull
> requests in early. I might drop things that come in too late.
Sorry for late. I am strugging for review and verification of exynos-drm-next tree.
This time, exynos drm tree will include below features,
- support runtime pm
- support dp panel dt binding using of graph concept.
- cleanup part of IPP enhancement patch series.
Now while I'm reviewing the cleanup part of IPP enhancement patch series, I found out a critical issue so as soon as I and original author resolve it, I will requst GIT PULL at least within next Monday.
Thanks,
Inki Dae
>
> I expect the x86 folks and others who are pretty regular to not be a
> problem (i.e. don't be a problem). Especially nouveau early is good
> for me if you have anything.
>
> Dave.
>
>
_______________________________________________
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 7:13 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 [this message]
2015-12-11 10:02 ` Russell King - ARM Linux
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=566A7799.1080604@samsung.com \
--to=inki.dae@samsung.com \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=rmk+kernel@arm.linux.org.uk \
--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