linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Damian <dhobsong@igel.co.jp>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 1/2] fbdev: sh_mobile_lcdc: Add YUV input support
Date: Wed, 02 Mar 2011 06:41:49 +0000	[thread overview]
Message-ID: <4D6DE6AD.9070509@igel.co.jp> (raw)
In-Reply-To: <1298456210-26519-2-git-send-email-dhobsong@igel.co.jp>

On 2011/03/01 17:59, Magnus Damm wrote:
> On Thu, Feb 24, 2011 at 12:38 PM, Damian<dhobsong@igel.co.jp>  wrote:
>> Ok, I see what you're saying. But if the SH_FB_YUV flag is disappearing, I
>> guess it makes sense to ditch the second patch in this series as well, since
>> that's just further abstraction (albeit locally).
>
> Yep, I think so. Thanks for your help!
Ok, then I will resubmit only the first patch of the series as
[PATCH v2] fbdev: sh_mobile_lcdc: Add YUV input support

Thanks,
Damian
>
> / magnus
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


-- 
Damian Hobson-Garcia
IGEL Co.,Ltd
http://www.igel.co.jp

      parent reply	other threads:[~2011-03-02  6:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-23 10:16 [PATCH 0/2] fbdev: sh_mobile_lcdc: YUV framebuffer support Damian Hobson-Garcia
2011-02-23 10:16 ` [PATCH 1/2] fbdev: sh_mobile_lcdc: Add YUV input support Damian Hobson-Garcia
2011-02-23 10:40   ` Guennadi Liakhovetski
2011-02-23 11:22   ` Damian
2011-02-23 14:58   ` James Simmons
2011-02-23 23:28   ` Magnus Damm
2011-02-24  3:38   ` Damian
2011-02-24  6:05   ` Geert Uytterhoeven
2011-03-01  3:13   ` Damian
2011-03-01  8:07   ` Geert Uytterhoeven
2011-03-01  8:25   ` Magnus Damm
2011-03-01 20:22     ` Geert Uytterhoeven
     [not found]       ` <AANLkTikFPdZ1ER=Cb59LL2CwBTA2NExSiVaTPzbGsE_o@mail.gmail.com>
2011-03-02 11:27         ` Alan Cox
2011-03-01  8:59   ` Magnus Damm
2011-03-02  6:41   ` Damian [this message]

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=4D6DE6AD.9070509@igel.co.jp \
    --to=dhobsong@igel.co.jp \
    --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).