From: Philipp Zabel <p.zabel@pengutronix.de>
To: Liu Ying <liu.y.victor@gmail.com>
Cc: Russell King <rmk+kernel@arm.linux.org.uk>,
DRI Development <dri-devel@lists.freedesktop.org>,
kernel@pengutronix.de, Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH 0/3] imx drm atomic mode setting fixups
Date: Fri, 08 Jul 2016 19:24:30 +0200 [thread overview]
Message-ID: <1467998670.2365.62.camel@pengutronix.de> (raw)
In-Reply-To: <CA+8Hj82R7yoSV3Zd+FuoJNSgR=oZ0AiOr1XFiMAGb36sAOGKxw@mail.gmail.com>
Hi Liu,
Am Freitag, den 08.07.2016, 17:38 +0800 schrieb Liu Ying:
[...]
> I'll respin to fix the LVDS bus format translation issue.
> To keep my patch set as small as possible, I'll leave your 3 patches
> for you to handle. Please consider to rebase.
Thanks, that works. I have rebased my changes on top:
git://git.pengutronix.de/git/pza/linux.git imx-drm/atomic
I plan to include this with my next pull request if there are no more
issues.
regards
Philipp
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-07-08 17:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 15:52 [PATCH 0/3] imx drm atomic mode setting fixups Philipp Zabel
2016-07-06 15:52 ` [PATCH 1/3] drm/imx: remove empty mode_set encoder callbacks Philipp Zabel
2016-07-06 15:52 ` [PATCH 2/3] drm/imx: store internal bus configuration in crtc state Philipp Zabel
2016-07-06 15:52 ` [PATCH 3/3] drm/imx: turn remaining container_of macros into inline functions Philipp Zabel
2016-07-07 7:44 ` [PATCH 0/3] imx drm atomic mode setting fixups Ying Liu
2016-07-07 8:29 ` Philipp Zabel
2016-07-08 9:38 ` Liu Ying
2016-07-08 17:24 ` Philipp Zabel [this message]
2016-07-11 2:56 ` Ying Liu
2016-07-11 8:46 ` Philipp Zabel
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=1467998670.2365.62.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@pengutronix.de \
--cc=liu.y.victor@gmail.com \
--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