From: Boris BREZILLON <boris.brezillon@free-electrons.com>
To: Dave Airlie <airlied@gmail.com>
Cc: yzq@rock-chips.com,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: rockchip and atmel kms drivers
Date: Wed, 17 Sep 2014 07:41:03 +0200 [thread overview]
Message-ID: <20140917074103.1e5f75d7@bbrezillon> (raw)
In-Reply-To: <CAPM=9tynWKfMnBCKuagZdE76Di3bLpbPSwSXsNoNNOv4x2PUZg@mail.gmail.com>
Hi Dave,
On Wed, 17 Sep 2014 11:18:44 +1000
Dave Airlie <airlied@gmail.com> wrote:
> Hey,
>
> So I notice we have two unreviewed drivers outstanding, the atmel
> hlcdc and the rockchips one, I'd like to suggest they you guys review
> each others work, they should be quite close in terms of functionality
> and you might spot some problems in your own code from reading the
> other driver.
Sure, I'll review the rockchip driver.
>
> I'm also hoping regular review will happen as well, but I think more
> cross-review is probably a good thing for new driver writers.
One more point, as stated in my cover letter, the HLCDC driver depends
on 2 other series ([1] and [2]), which I proposed after discussing it
with other KMS developers (Rob, Laurent and Thierry).
Could you take a look at these ones ?
Best Regards,
Boris
[1]http://lkml.iu.edu/hypermail/linux/kernel/1407.1/04171.html
[2]http://www.spinics.net/lists/kernel/msg1791681.html
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-09-17 5:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 1:18 rockchip and atmel kms drivers Dave Airlie
2014-09-17 5:41 ` Boris BREZILLON [this message]
2014-09-17 5:50 ` yaozq
2014-09-17 18:00 ` Boris BREZILLON
2014-09-18 9:55 ` yaozq
2014-09-17 16:05 ` Rob Clark
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=20140917074103.1e5f75d7@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=yzq@rock-chips.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.