From: Mike Isely <isely@isely.net>
To: Meelis Roos <mroos@linux.ee>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
Michael Krufky <mkrufky@linuxtv.org>,
Mike Isely at pobox <isely@pobox.com>
Subject: Re: pvrusb2 compile failure
Date: Mon, 7 Apr 2008 08:14:40 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0804070808120.23745@cnc.isely.net> (raw)
In-Reply-To: <Pine.SOC.4.64.0804070906490.15249@math.ut.ee>
On Mon, 7 Apr 2008, Meelis Roos wrote:
> Got this in todays 2.6.25-rc8+git
>
> CC [M] drivers/media/video/pvrusb2/pvrusb2-devattr.o
> drivers/media/video/pvrusb2/pvrusb2-devattr.c:178: error: unknown field 'flag_has_analogtuner' specified in initializer
> drivers/media/video/pvrusb2/pvrusb2-devattr.c:179: error: unknown field 'flag_has_composite' specified in initializer
> drivers/media/video/pvrusb2/pvrusb2-devattr.c:180: error: unknown field 'flag_has_svideo' specified in initializer
> drivers/media/video/pvrusb2/pvrusb2-devattr.c:182: error: unknown field 'digital_control_scheme' specified in initializer
> drivers/media/video/pvrusb2/pvrusb2-devattr.c:182: error: 'PVR2_DIGITAL_SCHEME_HAUPPAUGE' undeclared here (not in a function)
> drivers/media/video/pvrusb2/pvrusb2-devattr.c:183: error: unknown field 'led_scheme' specified in initializer
> drivers/media/video/pvrusb2/pvrusb2-devattr.c:183: error: 'PVR2_LED_SCHEME_HAUPPAUGE' undeclared here (not in a function)
> make[4]: *** [drivers/media/video/pvrusb2/pvrusb2-devattr.o] Error 1
This was supposed to be a patch that added badly-needed USB IDs to the
driver (via insert into a devic attribute data table), however it had
been cherry-picked out of a more recent patch series for the driver
where those additional fields / identifiers had also been defined.
Mike Krufky last night fixed his patch and posted it.
-Mike
--
Mike Isely
isely @ pobox (dot) com
PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8
prev parent reply other threads:[~2008-04-07 13:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 6:08 Meelis Roos
2008-04-07 13:14 ` Mike Isely [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=Pine.LNX.4.64.0804070808120.23745@cnc.isely.net \
--to=isely@isely.net \
--cc=isely@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mkrufky@linuxtv.org \
--cc=mroos@linux.ee \
/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
all inboxes | Powered by JetHome®