From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/5] ARM: vf610: Add DCU framebuffer driver for Vybrid VF610 platform
Date: Wed, 04 Sep 2013 10:33:21 +0000 [thread overview]
Message-ID: <52270C71.7080805@ti.com> (raw)
In-Reply-To: <81BA6E5E0BC2344391CABCEE22D1B6D8403CB3@039-SN1MPN1-002.039d.mgd.msft.net>
[-- Attachment #1: Type: text/plain, Size: 418 bytes --]
Hi,
On 03/09/13 11:21, Wang Huan-B18965 wrote:
> Hi, Jean-Christophe, Tomi,
>
> Could you please help to review these patches?
> Thanks!
There seemed to be some strong opinions that there should be a drm
driver for this hardware, instead of an fb driver. So as there seems to
be disagreements about this, I'll leave this series to Jean-Christophe,
who's the primary maintainer.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2013-09-04 10:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 8:01 [PATCH v3 0/5] ARM: vf610: Add DCU framebuffer driver for Vybrid VF610 platform Alison Wang
2013-08-15 8:01 ` [PATCH v3 1/5] ARM: dts: vf610: Add DCU and TCON nodes Alison Wang
2013-08-15 8:01 ` [PATCH v3 2/5] ARM: dts: vf610-twr: Enable DCU and TCON devices Alison Wang
2013-08-15 8:01 ` [PATCH v3 3/5] ARM: clk: vf610: Add DCU and TCON clock support Alison Wang
2013-08-15 8:01 ` [PATCH v3 4/5] fb: Add DCU framebuffer driver for Vybrid VF610 platform Alison Wang
2013-08-15 8:01 ` [PATCH v3 5/5] Documentation: DT: Add DCU framebuffer driver Alison Wang
2013-08-26 9:51 ` [PATCH v3 0/5] ARM: vf610: Add DCU framebuffer driver for Vybrid VF610 platform Wang Huan-B18965
2013-09-03 8:21 ` Wang Huan-B18965
2013-09-04 10:33 ` Tomi Valkeinen [this message]
2013-09-13 7:07 ` Wang Huan-B18965
2013-09-20 10:04 ` Tomi Valkeinen
2013-09-27 5:29 ` Wang Huan-B18965
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=52270C71.7080805@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).