From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Nicolas Ferre <nicolas.ferre@atmel.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: -next plans/status
Date: Mon, 3 Nov 2014 11:56:31 +0100 [thread overview]
Message-ID: <20141103115631.7ddfaf67@bbrezillon> (raw)
In-Reply-To: <CAPM=9tywXzvOFnpuhQBLy52KF0KEV6EYGB++B6sFKiFDzr9knA@mail.gmail.com>
Hi Dave,
On Mon, 3 Nov 2014 08:29:24 +1000
Dave Airlie <airlied@gmail.com> wrote:
> So since -rc5/6 cutoff last merge windows was so successful from my
> POV, I think I'll keep trucking with the idea.
>
> Things I have on my radar for this window, outside normal driver pull requests:
>
> a) rockchip drm - this needs IOMMU driver merged first so I can even
> compile it, on hold but shouldn't be a problem if the iommu driver
> gets merged somewhere first.
>
> b) atmel hlcdc - where are we on the precursor patches for this?
What do you mean by "precursor patches" ?
If by precursor patches you mean the dependencies of the DRM driver,
here is a quick status:
- The atmel-hlcdc [1] MFD driver has been taken by Lee Jones
- My series reworking the flip-work infrastructure [2] has been acked by
Rob and is waiting for you (I guess I should rebase it on
3.18-rcX or drm-next) ;-)
- My series sharing video bus format definitions between the V4L2 and
DRM subsystems [3] is still being discussed. AFAICT, the only blocking
point is that we need a documentation describing the available
formats and we don't know which format to use (DocBook or txt) and
where this documentation should be stored.
Regarding the driver itself, I still have to address Nicolas' (Ferre)
comments, and Thierry (Reding) was concerned by the proposed DT
binding (don't know if it's still the case).
Anyway, I really expect this driver to merged in 3.19 so let me know if
you see other blocking issues...
Best Regards,
Boris
[1]https://patchwork.ozlabs.org/patch/396808/
[2]http://thread.gmane.org/gmane.comp.video.dri.devel/110016
[3]https://lkml.org/lkml/2014/9/29/330
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-11-03 11:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-02 22:29 -next plans/status Dave Airlie
2014-11-03 7:56 ` Oded Gabbay
2014-11-03 10:56 ` Boris Brezillon [this message]
2014-11-04 22:10 ` Alex Deucher
2014-11-06 16:02 ` Thierry Reding
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=20141103115631.7ddfaf67@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=nicolas.ferre@atmel.com \
/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