From: Antti Palosaari <crope@iki.fi>
To: Chris Rankin <rankincj@yahoo.com>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>, linux-media@vger.kernel.org
Subject: Re: ERROR: "em28xx_add_into_devlist" [drivers/media/video/em28xx/em28xx.ko] undefined!
Date: Mon, 05 Sep 2011 03:24:54 +0300 [thread overview]
Message-ID: <4E6416D6.2060706@iki.fi> (raw)
In-Reply-To: <4E64148A.3010704@yahoo.com>
On 09/05/2011 03:15 AM, Chris Rankin wrote:
> On 05/09/11 00:46, Antti Palosaari wrote:
>> Moikka,
>> Current linux-media make gives error. Any idea what's wrong?
>>
>>
>> Kernel: arch/x86/boot/bzImage is ready (#1)
>> Building modules, stage 2.
>> MODPOST 1907 modules
>> ERROR: "em28xx_add_into_devlist"
>> [drivers/media/video/em28xx/em28xx.ko] undefined!
>> WARNING: modpost: Found 2 section mismatch(es).
>> To see full details build your kernel with:
>> 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
>> make[1]: *** [__modpost] Error 1
>> make: *** [modules] Error 2
>
> The function em28xx_add_into_devlist() should have been deleted as part
> of this change:
>
> http://git.linuxtv.org/media_tree.git?a=commitdiff;h=6c03e38b34dcfcdfa2f10cf984995a48f030f039
>
>
> Its only reference should have been removed at the same time.
git grep m28xx_add_into_devlis drivers/media/
drivers/media/video/em28xx/em28xx-cards.c:
em28xx_add_into_devlist(dev);
drivers/media/video/em28xx/em28xx.h:void em28xx_add_into_devlist(struct
em28xx *dev);
If you select em28xx-cards.c blob link you give you can see it is there
still for some reason.
regards
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2011-09-05 0:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-04 23:46 ERROR: "em28xx_add_into_devlist" [drivers/media/video/em28xx/em28xx.ko] undefined! Antti Palosaari
2011-09-05 0:15 ` Chris Rankin
2011-09-05 0:24 ` Antti Palosaari [this message]
2011-09-05 0:34 ` Chris Rankin
2011-09-05 13:57 ` Mauro Carvalho Chehab
2011-09-05 14:26 ` Chris Rankin
2011-09-05 0:24 ` Chris Rankin
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=4E6416D6.2060706@iki.fi \
--to=crope@iki.fi \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=rankincj@yahoo.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