From: Adrian Bunk <bunk@kernel.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: video4linux-list@redhat.com,
Mauro Carvalho Chehab <mchehab@redhat.com>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
lethal@linux-sh.org, Magnus Damm <damm@igel.co.jp>
Subject: Re: [PATCH] soc-camera: fix compile breakage on SH
Date: Wed, 15 Oct 2008 05:20:26 +0000 [thread overview]
Message-ID: <20081015052026.GC20183@cs181140183.pp.htv.fi> (raw)
In-Reply-To: <20081015033303.GC4710@cs181140183.pp.htv.fi>
On Wed, Oct 15, 2008 at 06:33:03AM +0300, Adrian Bunk wrote:
> On Tue, Oct 14, 2008 at 11:53:37PM +0200, Guennadi Liakhovetski wrote:
> > Fix Migo-R compile breakage caused by incomplete merge.
> >
> > Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> >
> > ---
> >
> > Hi Adrian,
>
> Hi Guennadi,
>
> > please see, if the patch below fixes it. Completely untested. Magnus,
> > could you please verify if it also works (of course, if it at least
> > compiles:-)) If it doesn't, please fix it along these lines, if it suits
> > your needs.
> >...
>
> it does compile.
>...
But it causes compile breakage elsewhere:
<-- snip -->
...
CC drivers/media/video/soc_camera_platform.o
drivers/media/video/soc_camera_platform.c: In function ‘soc_camera_platform_init’:
drivers/media/video/soc_camera_platform.c:49: error: ‘struct soc_camera_platform_info’ has no member named ‘power’
drivers/media/video/soc_camera_platform.c:50: error: ‘struct soc_camera_platform_info’ has no member named ‘power’
drivers/media/video/soc_camera_platform.c: In function ‘soc_camera_platform_release’:
drivers/media/video/soc_camera_platform.c:59: error: ‘struct soc_camera_platform_info’ has no member named ‘power’
drivers/media/video/soc_camera_platform.c:60: error: ‘struct soc_camera_platform_info’ has no member named ‘power’
make[4]: *** [drivers/media/video/soc_camera_platform.o] Error 1
<-- snip -->
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-10-15 5:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 18:39 sh/boards/mach-migor/setup.c build error Adrian Bunk
2008-10-14 21:53 ` [PATCH] soc-camera: fix compile breakage on SH Guennadi Liakhovetski
2008-10-15 3:33 ` Adrian Bunk
2008-10-15 5:20 ` Adrian Bunk [this message]
2008-10-15 6:28 ` Magnus Damm
2008-10-15 6:41 ` Guennadi Liakhovetski
2008-10-15 8:03 ` Magnus Damm
2008-10-15 8:26 ` Guennadi Liakhovetski
2008-10-15 8:55 ` Magnus Damm
2008-10-15 9:07 ` Guennadi Liakhovetski
2008-10-15 10:52 ` [PATCH v2] " Guennadi Liakhovetski
2008-10-16 23:08 ` Guennadi Liakhovetski
2008-10-16 23:16 ` [PATCH] " Guennadi Liakhovetski
2008-10-20 4:09 ` Paul Mundt
2008-10-20 7:02 ` Guennadi Liakhovetski
2008-10-20 12:45 ` Paul Mundt
2008-10-20 13:00 ` Guennadi Liakhovetski
2008-10-20 13:08 ` Paul Mundt
2008-10-20 17:44 ` Guennadi Liakhovetski
2008-10-21 3:45 ` Paul Mundt
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=20081015052026.GC20183@cs181140183.pp.htv.fi \
--to=bunk@kernel.org \
--cc=damm@igel.co.jp \
--cc=g.liakhovetski@gmx.de \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=video4linux-list@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