From: Haojian Zhuang <haojian.zhuang@gmail.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 0/4] Cleanups and fix for video/pxa3xx-gcu
Date: Thu, 06 Mar 2014 09:15:05 +0000 [thread overview]
Message-ID: <CAN1soZxOcUCUOSYWCYK7657nY_EDCTL=gLq9fmB7kEx6=ib4Ew@mail.gmail.com> (raw)
In-Reply-To: <1394035969-32420-1-git-send-email-zonque@gmail.com>
On Thu, Mar 6, 2014 at 5:09 PM, Daniel Mack <zonque@gmail.com> wrote:
> On 03/06/2014 03:09 AM, Haojian Zhuang wrote:
>> On Thu, Mar 6, 2014 at 12:12 AM, Daniel Mack <zonque@gmail.com> wrote:
>>> Here are some cleanups for the pxa3xx-gcu driver. Patch 3/4 is actually
>>> a real bugfix that is needed since the misc code doesn't set
>>> file->private_data for us implicitly anymore.
>>>
>>> The rest are just straight-forward cleanups.
>>>
>>> Thanks,
>>> Daniel
>>>
>>>
>>> Daniel Mack (4):
>>> video: pxa3xx-gcu: rename some symbols
>>> video: pxa3xx-gcu: pass around struct device *
>>> video: pxa3xx-gcu: provide an empty .open call
>>> video: pxa3xx-gcu: switch to devres functions
>>>
>>> drivers/video/pxa3xx-gcu.c | 191 +++++++++++++++++++--------------------------
>>> 1 file changed, 81 insertions(+), 110 deletions(-)
>>>
>
>> Acked-by: Haojian Zhuang <haojian.zhuang@gmail.com>
>
> Thanks Haojian!
>
> Given that this driver doesn't actually have any connection points to
> the framebuffer or video subsystem (despite its location) maybe you can
> just take these patches through your pxa tree? It's a PXA3xx specific
> device, after all. Jean-Christophe, Tomi - any objections?
>
If Jean or Tomi acked on this series, I can merge them into my pxa tree.
Best Regards
Haojian
next prev parent reply other threads:[~2014-03-06 9:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 16:12 [PATCH 0/4] Cleanups and fix for video/pxa3xx-gcu Daniel Mack
2014-03-06 2:09 ` Haojian Zhuang
2014-03-06 9:09 ` Daniel Mack
2014-03-06 9:15 ` Haojian Zhuang [this message]
2014-03-06 9:23 ` Tomi Valkeinen
2014-03-06 10:18 ` Daniel Mack
2014-03-06 10:30 ` Tomi Valkeinen
2014-03-06 10:53 ` Daniel Mack
2014-03-07 13:08 ` 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='CAN1soZxOcUCUOSYWCYK7657nY_EDCTL=gLq9fmB7kEx6=ib4Ew@mail.gmail.com' \
--to=haojian.zhuang@gmail.com \
--cc=linux-fbdev@vger.kernel.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).