All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Rankin <rankincj@yahoo.com>
To: Antti Palosaari <crope@iki.fi>
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 01:24:09 +0100	[thread overview]
Message-ID: <4E6416A9.9020206@yahoo.com> (raw)
In-Reply-To: <4E640DBB.8010504@iki.fi>

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

I think I see what's happened here. An extra reference to 
em28xx_add_into_devlist() has been added to em28xx_init_dev() at line 2888. This 
reference can be deleted because em28xx_init_extension() has been modified to 
add the struct em28xx to the devlist and then pass it to each extension's init() 
function all as a single operation.

Cheers,
Chris


      parent reply	other threads:[~2011-09-05  0:24 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
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 [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=4E6416A9.9020206@yahoo.com \
    --to=rankincj@yahoo.com \
    --cc=crope@iki.fi \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.