From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Kassey Lee <kassey1216@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-media@vger.kernel.org, g.liakhovetski@gmx.de,
Kassey Lee <ygli@marvell.com>, Daniel Drake <dsd@laptop.org>,
ytang5@marvell.com, leiwen@marvell.com, qingx@marvell.com
Subject: Re: [PATCH 2/8] marvell-cam: Separate out the Marvell camera core
Date: Thu, 16 Jun 2011 21:40:54 -0300 [thread overview]
Message-ID: <4DFAA296.903@infradead.org> (raw)
In-Reply-To: <BANLkTikztbcm_+PR5oFVB+v0Jn4q8GCVTQ@mail.gmail.com>
Em 15-06-2011 23:30, Kassey Lee escreveu:
> 2011/6/14 Jonathan Corbet <corbet@lwn.net>:
>> On Tue, 14 Jun 2011 10:58:47 +0800
>> Kassey Lee <kassey1216@gmail.com> wrote:
>>>> + /*
>>>> + * Try to find the sensor.
>>>> + */
>>>> + cam->sensor_addr = ov7670_info.addr;
>>>> + cam->sensor = v4l2_i2c_new_subdev_board(&cam->v4l2_dev,
>>>> + &cam->i2c_adapter, &ov7670_info, NULL);
>>> I do not thinks so.
>>
>> I don't understand what this comment is meant to mean...?
> this should be move out to arch/arm/mach-xxx/board.c
Please drop the parts that you're not commenting. It is very hard to find a one-line
comment in the middle of a long patch, especially since you don't even add blank
lines before/after it.
With respect to your comment, it doesn't makes much sense,as cafe_ccic
runs on OLPC 1 hardware (at least the version I have here) is x86-based.
So, I'm not seeing any reason why not apply patch 2/8.
Applying on my tree.
Mauro.
next prev parent reply other threads:[~2011-06-17 0:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 17:46 Refactor cafe_ccic and add Armada 610 driver [V2] Jonathan Corbet
2011-06-11 17:46 ` [PATCH 1/8] marvell-cam: Move cafe-ccic into its own directory Jonathan Corbet
[not found] ` <BANLkTikXATbgOZQbzaj4sQEmELsdpNobfQ@mail.gmail.com>
2011-06-14 14:23 ` Jonathan Corbet
2011-06-15 2:01 ` Kassey Lee
2011-06-15 11:37 ` Mauro Carvalho Chehab
2011-06-11 17:46 ` [PATCH 2/8] marvell-cam: Separate out the Marvell camera core Jonathan Corbet
2011-06-14 2:58 ` Kassey Lee
2011-06-14 14:49 ` Jonathan Corbet
2011-06-16 2:30 ` Kassey Lee
2011-06-16 3:12 ` Kassey Lee
2011-06-16 15:27 ` Jonathan Corbet
2011-06-17 0:45 ` Mauro Carvalho Chehab
2011-06-17 3:11 ` Kassey Lee
2011-06-22 22:12 ` Jonathan Corbet
2011-06-27 9:23 ` Kassey Lee
2011-06-17 0:40 ` Mauro Carvalho Chehab [this message]
2011-06-17 2:51 ` Kassey Lee
2011-06-11 17:46 ` [PATCH 3/8] marvell-cam: Pass sensor parameters from the platform Jonathan Corbet
2011-06-11 17:46 ` [PATCH 4/8] marvell-cam: Remove the "untested" comment Jonathan Corbet
2011-06-11 17:46 ` [PATCH 5/8] marvell-cam: Move Cafe-specific register definitions to cafe-driver.c Jonathan Corbet
2011-06-11 17:46 ` [PATCH 6/8] marvell-cam: Right-shift i2c slave ID's in the cafe driver Jonathan Corbet
2011-06-17 0:51 ` Mauro Carvalho Chehab
2011-06-11 17:46 ` [PATCH 7/8] marvell-cam: Allocate the i2c adapter in the platform driver Jonathan Corbet
2011-06-11 17:46 ` [PATCH 8/8] marvell-cam: Basic working MMP camera driver Jonathan Corbet
2011-06-16 2:37 ` Kassey Lee
2011-06-16 15:17 ` Jonathan Corbet
2011-06-16 19:44 ` Sylwester Nawrocki
2011-06-17 1:15 ` 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=4DFAA296.903@infradead.org \
--to=mchehab@infradead.org \
--cc=corbet@lwn.net \
--cc=dsd@laptop.org \
--cc=g.liakhovetski@gmx.de \
--cc=kassey1216@gmail.com \
--cc=leiwen@marvell.com \
--cc=linux-media@vger.kernel.org \
--cc=qingx@marvell.com \
--cc=ygli@marvell.com \
--cc=ytang5@marvell.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