From: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-fbdev@vger.kernel.org, linux-media@vger.kernel.org,
magnus.damm@gmail.com, Mauro Carvalho Chehab <mchehab@redhat.com>
Subject: Re: [PATCH v3 0/3] fbdev: Add FOURCC-based format configuration API
Date: Fri, 11 Nov 2011 16:31:13 +0000 [thread overview]
Message-ID: <4EBD4DD1.7030809@gmx.de> (raw)
In-Reply-To: <201109182249.39536.laurent.pinchart@ideasonboard.com>
On 09/18/2011 08:49 PM, Laurent Pinchart wrote:
>> As the second patch has nothing to do with fbdev it should go mainline via
>> V4L2. Any problems/comments?
>
> The NV24/42 patch will need to reach mainline before the sh_mobile_lcdc YUV
> API patch, or compilation will break.
>
> Mauro, what's your preference ? Should the patch go through the media tree ?
> If so, how should we synchronize it with the fbdev tree ? Should I push it to
> 3.2 ?
ping
What's going on? I could carry the patch but I'd want an Ack to do so.
Best regards,
Florian Tobias Schandinat
next prev parent reply other threads:[~2011-11-11 16:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 11:18 [PATCH v3 0/3] fbdev: Add FOURCC-based format configuration API Laurent Pinchart
2011-08-31 11:18 ` [PATCH v3 1/3] " Laurent Pinchart
2011-11-20 2:00 ` Florian Tobias Schandinat
2011-11-20 10:55 ` Laurent Pinchart
2011-11-24 10:50 ` Laurent Pinchart
2011-11-25 22:09 ` Florian Tobias Schandinat
2011-11-28 11:12 ` Laurent Pinchart
2011-08-31 11:18 ` [PATCH v3 2/3] v4l: Add V4L2_PIX_FMT_NV24 and V4L2_PIX_FMT_NV42 formats Laurent Pinchart
2011-11-11 18:41 ` [PATCH v3 2/3] v4l: Add V4L2_PIX_FMT_NV24 and V4L2_PIX_FMT_NV42 Mauro Carvalho Chehab
2011-08-31 11:18 ` [PATCH v3 3/3] fbdev: sh_mobile_lcdc: Support FOURCC-based format API Laurent Pinchart
2011-09-18 19:49 ` [PATCH v3 0/3] fbdev: Add FOURCC-based format configuration API Florian Tobias Schandinat
2011-09-18 20:49 ` Laurent Pinchart
2011-11-11 16:31 ` Florian Tobias Schandinat [this message]
2011-11-11 18:41 ` Mauro Carvalho Chehab
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=4EBD4DD1.7030809@gmx.de \
--to=florianschandinat@gmx.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mchehab@redhat.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 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).