public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <snjw23@gmail.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [GIT PATCHES FOR 2.6.38] Videbuf2 framework, NOON010PC30 sensor driver and s5p-fimc updates
Date: Wed, 12 Jan 2011 17:19:10 +0100	[thread overview]
Message-ID: <4D2DD47E.8030307@gmail.com> (raw)
In-Reply-To: <4D2CD262.2070601@redhat.com>

On 01/11/2011 10:57 PM, Mauro Carvalho Chehab wrote:
> Em 03-01-2011 14:48, Sylwester Nawrocki escreveu:
>> Hi Mauro,
>>
>> Please pull from our tree for the following items:
>>
>> 4. s5p-fimc driver conversion to Videbuf2 and multiplane ext. and various
>>     driver updates and bugfixes,
>> 5. Siliconfile NOON010PC30 sensor subdev driver,
> 
> Those patches seem ok. I have just a couple comments about them. See bellow.
> 
> After having them solved, please send the patches against my vb2 test tree:
> 
> 	git://linuxtv.org/mchehab/experimental.git vb2_test
> 
> I've tested already vb2 with vivi. I'll be testing them now with saa7134.
> After testing it, I'll give you a feedback about vb2 and, if ok, I'll merge
> both multiplane and vb2 on my main tree.
> 
>> Hyunwoong Kim (5):
>>        [media] s5p-fimc: fix the value of YUV422 1-plane formats
> 
> I don't have an arm cross-compilation handy, but... that means that, before this
> patch, compilation were broken? If so, please, don't do that, as it breaks bisect.
> Instead, merge the patch withthe one that broke compilation.

No, the purpose of this patch is to only change the values programmed
into the H/W registers. The patch summary line seem not to be 
too accurate. This patch doesn't fix any compilation problems. 

I always try to test the patches against compilation breakage one by one.
But this time unfortunately I didn't do enough tests of the mem2mem
conversion changes when sending the pull request.


Regards,
Sylwester




  parent reply	other threads:[~2011-01-12 16:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-03 16:48 [GIT PATCHES FOR 2.6.38] Videbuf2 framework, NOON010PC30 sensor driver and s5p-fimc updates Sylwester Nawrocki
2011-01-11 18:23 ` Mauro Carvalho Chehab
2011-01-11 16:42   ` Pawel Osciak
2011-01-11 19:06     ` Mauro Carvalho Chehab
2011-01-11 20:19 ` Mauro Carvalho Chehab
2011-01-12 10:25   ` Marek Szyprowski
2011-01-12 18:49     ` Mauro Carvalho Chehab
2011-01-13  3:05       ` Pawel Osciak
2011-01-13 12:18         ` Mauro Carvalho Chehab
2011-01-12 20:23     ` Mauro Carvalho Chehab
2011-01-13  8:46       ` Andrzej Pietrasiewicz
2011-01-13 12:13         ` Andrzej Pietrasiewicz
2011-01-13 13:04           ` Mauro Carvalho Chehab
2011-01-13 12:58         ` Mauro Carvalho Chehab
2011-01-16 15:11           ` Mauro Carvalho Chehab
2011-01-11 21:31 ` Mauro Carvalho Chehab
2011-01-11 21:57 ` Mauro Carvalho Chehab
2011-01-12  2:47   ` Pawel Osciak
2011-01-12 16:19   ` Sylwester Nawrocki [this message]
2011-01-11 22:08 ` 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=4D2DD47E.8030307@gmail.com \
    --to=snjw23@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=mchehab@redhat.com \
    --cc=s.nawrocki@samsung.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