From: Greg KH <gregkh@suse.de>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-media@vger.kernel.org
Subject: Re: linux-next: Tree for March 11 (staging/multimedia)
Date: Wed, 11 Mar 2009 11:24:11 -0700 [thread overview]
Message-ID: <20090311182411.GA6501@suse.de> (raw)
In-Reply-To: <49B80140.5000304@oracle.com>
On Wed, Mar 11, 2009 at 11:21:52AM -0700, Randy Dunlap wrote:
> Greg KH wrote:
> > On Wed, Mar 11, 2009 at 10:12:39AM -0700, Randy Dunlap wrote:
> >> Stephen Rothwell wrote:
> >>> Hi all,
> >>>
> >>> Changes since 20090310:
> >>
> >> drivers/staging/go7007/go7007-v4l2.c:1830: error: 'VID_TYPE_CAPTURE' undeclared here (not in a function)
> >
> > Odd, nothing has changed in this driver, is this a v4l api change?
>
> I don't know if the vl4 API changed, but this error has been around
> for some time now. Just because it's just now being reported is one
> change. Surely other people build these drivers. ???
I do, and don't seem to get this error.
Ah, it's a CONFIG_VIDEO_V4L1_COMPAT issue. I'll see what needs to do to
fix this up.
thanks,
greg k-h
next prev parent reply other threads:[~2009-03-11 18:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 11:59 linux-next: Tree for March 11 Stephen Rothwell
2009-03-11 17:12 ` linux-next: Tree for March 11 (staging/multimedia) Randy Dunlap
2009-03-11 18:11 ` Greg KH
2009-03-11 18:21 ` Randy Dunlap
2009-03-11 18:24 ` Greg KH [this message]
2009-03-11 18:27 ` Hans Verkuil
2009-03-11 17:36 ` linux-next: Tree for March 11 (tracing) Randy Dunlap
2009-03-12 16:17 ` Randy Dunlap
2009-03-12 16:26 ` Steven Rostedt
2009-03-12 16:32 ` Randy Dunlap
2009-03-18 15:46 ` Randy Dunlap
2009-03-18 16:06 ` Ingo Molnar
2009-03-18 16:13 ` Randy Dunlap
2009-03-18 16:32 ` Ingo Molnar
2009-03-18 16:44 ` Randy Dunlap
2009-03-18 16:49 ` Ingo Molnar
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=20090311182411.GA6501@suse.de \
--to=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.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).