From: Greg KH <greg@kroah•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, Hans Verkuil <hverkuil@xs4all•nl>,
Mauro Carvalho Chehab <mchehab@infradead•org>,
Dean Anderson <dean@sensoray•com>
Subject: Re: linux-next: ldp build failure
Date: Tue, 3 Jun 2008 22:24:03 -0700 [thread overview]
Message-ID: <20080604052403.GA13998@kroah.com> (raw)
In-Reply-To: <20080604150819.ec26f31f.sfr@canb.auug.org.au>
On Wed, Jun 04, 2008 at 03:08:19PM +1000, Stephen Rothwell wrote:
> Hi Greg,
>
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> drivers/media/video/s2255drv.c:1659: error: unknown field 'vidioc_enum_fmt_cap' specified in initializer
> drivers/media/video/s2255drv.c:1659: warning: initialization from incompatible pointer type
> drivers/media/video/s2255drv.c:1660: error: unknown field 'vidioc_g_fmt_cap' specified in initializer
> drivers/media/video/s2255drv.c:1660: warning: initialization from incompatible pointer type
> drivers/media/video/s2255drv.c:1661: error: unknown field 'vidioc_try_fmt_cap' specified in initializer
> drivers/media/video/s2255drv.c:1661: warning: initialization from incompatible pointer type
> drivers/media/video/s2255drv.c:1662: error: unknown field 'vidioc_s_fmt_cap' specified in initializer
> drivers/media/video/s2255drv.c:1662: warning: initialization from incompatible pointer type
>
> Caused by commit 7ddf62fca6b9be8867204dfcd062bca43a75bae6 ("V4L/DVB
> (7949): videodev: renamed the vidioc_*_fmt_* callbacks") from the v4l-dvb
> tree. I applied the patch below.
Thanks for the patch, I'll apply it when I resend the driver to Mauro,
hopefully tomorrow :)
thanks,
greg k-h
prev parent reply other threads:[~2008-06-04 5:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 5:08 linux-next: ldp build failure Stephen Rothwell
2008-06-04 5:24 ` Greg KH [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=20080604052403.GA13998@kroah.com \
--to=greg@kroah$(echo .)com \
--cc=dean@sensoray$(echo .)com \
--cc=hverkuil@xs4all$(echo .)nl \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mchehab@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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