From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ap325: use edge control for ov772x camera
Date: Mon, 13 Apr 2009 21:02:29 +0000 [thread overview]
Message-ID: <20090413210229.GB14847@linux-sh.org> (raw)
In-Reply-To: <uprfhgibw.wl%morimoto.kuninori@renesas.com>
On Mon, Apr 13, 2009 at 03:40:04PM +0900, Kuninori Morimoto wrote:
>
> Signed-off-by: Kuninori Morimoto <morimoto.kuninori@renesas.com>
> ---
> This patch is for Linux 2.6.30-rc1
>
> arch/sh/boards/board-ap325rxa.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/arch/sh/boards/board-ap325rxa.c b/arch/sh/boards/board-ap325rxa.c
> index 912458f..39e4691 100644
> --- a/arch/sh/boards/board-ap325rxa.c
> +++ b/arch/sh/boards/board-ap325rxa.c
> @@ -349,6 +349,7 @@ static int ov7725_power(struct device *dev, int mode)
> static struct ov772x_camera_info ov7725_info = {
> .buswidth = SOCAM_DATAWIDTH_8,
> .flags = OV772X_FLAG_VFLIP | OV772X_FLAG_HFLIP,
> + .edgectrl = OV772X_AUTO_EDGECTRL(0xf, 0),
> .link = {
> .power = ov7725_power,
> },
While I don't mind empty changelogs for obvious and trivial changes,
things like this really want some explanation. I don't know if this fixes
a regression, adds a new feature, what the impact is for different
versions of the board, etc.
If a change is not immediately obvious from the description, you really
want a changelog for it.
prev parent reply other threads:[~2009-04-13 21:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 6:40 [PATCH] ap325: use edge control for ov772x camera Kuninori Morimoto
2009-04-13 21:02 ` Paul Mundt [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=20090413210229.GB14847@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@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