From: Philipp Zabel <p.zabel@pengutronix.de>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Russell King <rmk+kernel@arm.linux.org.uk>,
dri-devel@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH v3 00/10] imx drm atomic mode setting conversion
Date: Tue, 12 Jul 2016 18:48:57 +0200 [thread overview]
Message-ID: <1468342137.2796.28.camel@pengutronix.de> (raw)
In-Reply-To: <20160712125159.GY23520@phenom.ffwll.local>
Am Dienstag, den 12.07.2016, 14:51 +0200 schrieb Daniel Vetter:
> On Mon, Jul 04, 2016 at 03:40:29PM +0800, Liu Ying wrote:
> > Hi,
> >
> > This is the v3 patch set to convert imx drm into atomic mode setting.
> > It takes 3 phases to achieve the goal.
> >
> > v2->v3:
> > * Rebase onto Daniel Vetter's open git branch topic/drm-misc so that
> > we may better support nonblock atomic commit with the aid from
> > drm atomic helper.
> > * Remove dw-hdmi bridge driver's legacy drm_connector_funcs struture
> > step-by-step instead of doing that in patch 04/10 directly.
> > So, patch 08/10 in this set is newly introduced.
>
> Assuming all my feedback has been addressed:
>
> Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>
> I'd just go ahead and send Dave Airlie a pull req for this, but hurry up
> to make it into 4.8.
> -Daniel
Will do, thanks.
regards
Philipp
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2016-07-12 16:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 7:40 [PATCH v3 00/10] imx drm atomic mode setting conversion Liu Ying
2016-07-04 7:40 ` [PATCH v3 01/10] drm/imx: ipuv3 plane: Check different types of plane separately Liu Ying
2016-07-04 7:40 ` [PATCH v3 02/10] gpu: ipu-v3: ipu-dmfc: Use static DMFC FIFO allocation mechanism Liu Ying
2016-07-04 7:40 ` [PATCH v3 03/10] drm/imx: atomic phase 1: Use transitional atomic CRTC and plane helpers Liu Ying
2016-08-13 10:11 ` Russell King - ARM Linux
2016-08-13 10:45 ` Russell King - ARM Linux
2016-08-13 11:29 ` Russell King - ARM Linux
2016-08-13 14:09 ` Russell King - ARM Linux
2016-08-13 15:00 ` Russell King - ARM Linux
2016-08-14 9:44 ` Daniel Vetter
2016-08-14 10:46 ` Daniel Vetter
2016-08-14 11:43 ` Peter Senna Tschudin
2016-08-15 6:21 ` Ying Liu
2016-07-04 7:40 ` [PATCH v3 04/10] drm/imx: atomic phase 2 step 1: Wire up state ->reset, ->duplicate and ->destroy Liu Ying
2016-07-04 7:40 ` [PATCH v3 05/10] drm/imx: atomic phase 2 step 2: Track plane_state->fb correctly in ->page_flip Liu Ying
2016-07-04 7:40 ` [PATCH v3 06/10] drm/imx: Remove encoders' ->prepare callbacks Liu Ying
2016-07-04 7:40 ` [PATCH v3 07/10] drm/imx: atomic phase 3 step 1: Use atomic configuration Liu Ying
2016-07-04 7:40 ` [PATCH v3 08/10] drm/bridge: dw-hdmi: Remove the legacy drm_connector_funcs structure Liu Ying
2016-07-04 7:40 ` [PATCH v3 09/10] drm/imx: atomic phase 3 step 2: Legacy callback fixups Liu Ying
2016-07-04 7:40 ` [PATCH v3 10/10] drm/imx: atomic phase 3 step 3: Advertise DRIVER_ATOMIC Liu Ying
2016-07-12 12:51 ` [PATCH v3 00/10] imx drm atomic mode setting conversion Daniel Vetter
2016-07-12 16:48 ` Philipp Zabel [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1468342137.2796.28.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=rmk+kernel@arm.linux.org.uk \
/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