From: Manfred Schlaegl <manfred.schlaegl@gmx.at>
To: Philipp Zabel <p.zabel@pengutronix.de>, Stefan Agner <stefan@agner.ch>
Cc: dri-devel@lists.freedesktop.org, thierry.reding@gmail.com,
airlied@linux.ie, daniel.vetter@ffwll.ch,
jianwei.wang.chn@gmail.com, alison.wang@freescale.com,
meng.yi@nxp.com, linux@arm.linux.org.uk, denis@eukrea.com,
eric@eukrea.com, ville.syrjala@linux.intel.com,
linux-kernel@vger.kernel.org, tomi.valkeinen@ti.com,
boris.brezillon@free-electrons.com
Subject: Re: [PATCH v2 0/3] drm: introduce bus_flags for pixel clock polarity
Date: Thu, 25 Feb 2016 08:59:17 +0100 [thread overview]
Message-ID: <56CEB455.7080608@gmx.at> (raw)
In-Reply-To: <1456309726.3396.31.camel@pengutronix.de>
On 2016-02-24 11:28, Philipp Zabel wrote:
> Am Dienstag, den 23.02.2016, 15:30 -0800 schrieb Stefan Agner:
>> Any comments on this?
>
> None other that I'm all in favor. consider patch 2
> Acked-by: Philipp Zabel <p.zabel@pengutronix.de>
>
Same here!
Acked-by: Manfred Schlaegl <manfred.schlaegl@gmx.at>
regards
Manfred
next prev parent reply other threads:[~2016-02-25 7:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 21:57 [PATCH v2 0/3] drm: introduce bus_flags for pixel clock polarity Stefan Agner
2016-02-08 21:57 ` [PATCH v2 1/3] drm/fsl-dcu: use mode flags for hsync/vsync polarity Stefan Agner
2016-02-25 16:48 ` Thierry Reding
2016-02-25 23:55 ` Stefan Agner
2016-02-08 21:57 ` [PATCH v2 2/3] drm: introduce bus_flags in drm_display_info Stefan Agner
2016-02-08 21:57 ` [PATCH v2 3/3] drm/fsl-dcu: use bus_flags for pixel clock polarity Stefan Agner
2016-02-23 23:30 ` [PATCH v2 0/3] drm: introduce " Stefan Agner
2016-02-24 10:28 ` Philipp Zabel
2016-02-25 7:59 ` Manfred Schlaegl [this message]
2016-02-24 11:06 ` Tomi Valkeinen
2016-02-24 19:02 ` Stefan Agner
2016-02-24 20:17 ` Ville Syrjälä
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=56CEB455.7080608@gmx.at \
--to=manfred.schlaegl@gmx.at \
--cc=airlied@linux.ie \
--cc=alison.wang@freescale.com \
--cc=boris.brezillon@free-electrons.com \
--cc=daniel.vetter@ffwll.ch \
--cc=denis@eukrea.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@eukrea.com \
--cc=jianwei.wang.chn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=meng.yi@nxp.com \
--cc=p.zabel@pengutronix.de \
--cc=stefan@agner.ch \
--cc=thierry.reding@gmail.com \
--cc=tomi.valkeinen@ti.com \
--cc=ville.syrjala@linux.intel.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;
as well as URLs for NNTP newsgroup(s).