From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: linux-next: Tree for Sept 28 (media/video/mt9p031.c)
Date: Wed, 28 Sep 2011 15:31:11 -0700 [thread overview]
Message-ID: <4E83A02F.2020309@xenotime.net> (raw)
In-Reply-To: <4E839FCB.7050403@xenotime.net>
On 09/28/11 15:29, Randy Dunlap wrote:
> On 09/28/11 03:04, Stephen Rothwell wrote:
>> Hi all,
>
>
> a. Source file needs <linux/module.h> added to it unless the dropping
> of the moduleh tree for today already contained that patch.
>
> b. Build errors after adding <linux/module.h>:
>
> when CONFIG_MEDIA_CONTROLLER is not enabled
> and CONFIG_VIDEO_V4L2_SUBDEV_API is not enabled:
>
>
> drivers/media/video/mt9p031.c:443:3: error: implicit declaration of function 'v4l2_subdev_get_try_format'
> drivers/media/video/mt9p031.c:457:3: error: implicit declaration of function 'v4l2_subdev_get_try_crop'
> drivers/media/video/mt9p031.c:888:42: error: 'struct v4l2_subdev' has no member named 'entity'
Similar problems with drivers/media/video/mt9t001.c.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-09-28 22:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 10:04 linux-next: Tree for Sept 28 Stephen Rothwell
2011-09-28 22:11 ` linux-next: Tree for Sept 28 (mrst) Randy Dunlap
2011-12-05 18:39 ` Randy Dunlap
2011-12-05 18:41 ` Ingo Molnar
2011-12-05 19:10 ` Alan Cox
2011-09-28 22:29 ` linux-next: Tree for Sept 28 (media/video/mt9p031.c) Randy Dunlap
2011-09-28 22:31 ` Randy Dunlap [this message]
2011-09-30 21:34 ` [PATCH] drivers/media: fix dependencies in video mt9t001/mt9p031 Paul Gortmaker
2011-09-30 22:38 ` Randy Dunlap
2011-10-06 3:02 ` Stephen Rothwell
2011-10-08 10:52 ` Mauro Carvalho Chehab
2011-10-09 3:39 ` Paul Gortmaker
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=4E83A02F.2020309@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).