From: Tony Lindgren <tony@atomide.com>
To: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>,
Enric Balletbo i Serra <eballetbo@gmail.com>,
bcousson@baylibre.com, linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/1] ARM: OMAP2+: pdata-quirks: add legacy display init for IGEPv2 board
Date: Wed, 9 Oct 2013 07:52:30 -0700 [thread overview]
Message-ID: <20131009145230.GX8313@atomide.com> (raw)
In-Reply-To: <5255077A.4010702@collabora.co.uk>
* Javier Martinez Canillas <javier.martinez@collabora.co.uk> [131009 00:45]:
> On 10/09/2013 08:02 AM, Tomi Valkeinen wrote:
> > Hi Tony,
> >
> > On 09/10/13 00:11, Tony Lindgren wrote:
> >> * Javier Martinez Canillas <javier.martinez@collabora.co.uk> [131004 20:00]:
> >>> IGEPv2 board has both an DVI and TFP410 video interfaces but
> >>> DSS support for DeviceTree has not yet landed in mainline so
> >>> is necessary to init the displays using legacy platform code.
> >>
> >> Thanks, applying into omap-for-v3.13/quirk.
> >
> > Can you remove the patch from your branch? It had bug, and I had some
> > questions related to it.
>
> I noticed about the bug (a duplicated pdata_quirks) just after sending the patch
> so I fixed on a v2 [1].
OK dropping it as I did not push it out yet. Will apply the version
with Tomi's ack.
Regards,
Tony
> [1]: http://www.spinics.net/lists/linux-omap/msg98257.html
next prev parent reply other threads:[~2013-10-09 14:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-05 2:51 [PATCH 1/1] ARM: OMAP2+: pdata-quirks: add legacy display init for IGEPv2 board Javier Martinez Canillas
2013-10-08 21:11 ` Tony Lindgren
2013-10-09 6:02 ` Tomi Valkeinen
2013-10-09 7:36 ` Javier Martinez Canillas
2013-10-09 14:52 ` Tony Lindgren [this message]
2013-10-09 6:00 ` Tomi Valkeinen
2013-10-09 7:44 ` Javier Martinez Canillas
2013-10-09 7:47 ` Tomi Valkeinen
2013-10-09 7:54 ` Javier Martinez Canillas
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=20131009145230.GX8313@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=eballetbo@gmail.com \
--cc=javier.martinez@collabora.co.uk \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.