From: Tony Prisk <linux@prisktech.co.nz>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHv3 0/6] fb: vt8500: patches for 3.10
Date: Thu, 04 Apr 2013 05:27:58 +0000 [thread overview]
Message-ID: <515D0F5E.5010805@prisktech.co.nz> (raw)
In-Reply-To: <1364926838-6721-1-git-send-email-linux@prisktech.co.nz>
On 03/04/13 07:20, Tony Prisk wrote:
> V3 Changes:
> Tidied up patch 1 as requested by Jean-Christophe - Makes the patch much
> simpler.
>
> V2 Changes:
> Split the SoC and board portions of the binding into their respective files.
> Removed the forced non-interlaced code from wm8505fb.c and vt8500lcdfb.c
>
> Julia Lawall (1):
> drivers/video/wm8505fb.c: use devm_ functions
>
> Tony Prisk (5):
> video: vt8500: Make wmt_ge_rops optional
> video: vt8500: Remove unused platform_data/video-vt8500lcdfb.h
> video: vt8500: Correct descriptions in video/Kconfig
> video: vt8500: Adjust contrast in wm8505 framebuffer driver.
> video: fb: vt8500: Convert framebuffer drivers to standardized
> binding
>
> .../devicetree/bindings/video/via,vt8500-fb.txt | 48 ++-----
> .../devicetree/bindings/video/wm,wm8505-fb.txt | 32 +++--
> arch/arm/boot/dts/vt8500-bv07.dts | 34 ++---
> arch/arm/boot/dts/vt8500.dtsi | 4 +-
> arch/arm/boot/dts/wm8505-ref.dts | 34 ++---
> arch/arm/boot/dts/wm8505.dtsi | 4 +-
> arch/arm/boot/dts/wm8650-mid.dts | 36 +++--
> arch/arm/boot/dts/wm8650.dtsi | 4 +-
> arch/arm/boot/dts/wm8850-w70v2.dts | 40 +++---
> arch/arm/boot/dts/wm8850.dtsi | 4 +-
> drivers/video/Kconfig | 37 +++--
> drivers/video/vt8500lcdfb.c | 55 +++-----
> drivers/video/wm8505fb.c | 144 ++++++--------------
> drivers/video/wmt_ge_rops.h | 23 ++++
> include/linux/platform_data/video-vt8500lcdfb.h | 31 -----
> 15 files changed, 211 insertions(+), 319 deletions(-)
> delete mode 100644 include/linux/platform_data/video-vt8500lcdfb.h
>
Tomi,
If no one has any further comments, are you still prepared to take this
series?
If so, I will send a pull-request.
With regards to the earlier concern about your current patch series, I
think its easiest if you do take this series then you could do a fixup
patch if this one is merged first. From what I remember of your series,
it is basically a rename of of_get_display_timings() to
of_get_display_timing() and some new code which I don't use. Seems a
rather trivial patch for a fixup later.
Let me know what you want to do.
Regards
Tony P
next prev parent reply other threads:[~2013-04-04 5:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 18:20 [PATCHv3 0/6] fb: vt8500: patches for 3.10 Tony Prisk
2013-04-02 18:20 ` [PATCHv3 1/6] video: vt8500: Make wmt_ge_rops optional Tony Prisk
2013-04-02 18:20 ` [PATCHv3 2/6] video: vt8500: Remove unused platform_data/video-vt8500lcdfb.h Tony Prisk
2013-04-02 18:20 ` [PATCHv3 3/6] video: vt8500: Correct descriptions in video/Kconfig Tony Prisk
2013-04-02 18:20 ` [PATCHv3 4/6] drivers/video/wm8505fb.c: use devm_ functions Tony Prisk
2013-04-02 18:20 ` [PATCHv3 5/6] video: vt8500: Adjust contrast in wm8505 framebuffer driver Tony Prisk
2013-04-02 18:20 ` [PATCHv3 6/6] video: fb: vt8500: Convert framebuffer drivers to standardized binding Tony Prisk
2013-04-03 4:33 ` [PATCHv3 0/6] fb: vt8500: patches for 3.10 Jean-Christophe PLAGNIOL-VILLARD
2013-04-04 5:27 ` Tony Prisk [this message]
2013-04-04 10:16 ` Tomi Valkeinen
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=515D0F5E.5010805@prisktech.co.nz \
--to=linux@prisktech.co.nz \
--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).