The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Steve French <smfrench@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Matthew Garrett <mjg@redhat.com>,
	"Lee, Chun-Yi" <joeyli.kernel@gmail.com>
Subject: Re: undefined reference to `sparse_keymap_free'
Date: Mon, 11 Apr 2011 22:58:51 -0700	[thread overview]
Message-ID: <20110412055851.GA1854@core.coreip.homeip.net> (raw)
In-Reply-To: <20110411224819.b349025a.akpm@linux-foundation.org>

On Mon, Apr 11, 2011 at 10:48:19PM -0700, Andrew Morton wrote:
> (cc's added)
> 
> On Mon, 11 Apr 2011 23:18:04 -0500 Steve French <smfrench@gmail.com> wrote:
> 
> > 2.6.38-rc3 build error:
> > 
> > drivers/built-in.o: In function `msi_laptop_input_destroy':
> > msi-laptop.c:(.text+0x1a3be1): undefined reference to `sparse_keymap_free'
> > drivers/built-in.o: In function `msi_send_touchpad_key':
> > msi-laptop.c:(.text+0x1a3c45): undefined reference to
> > `sparse_keymap_report_event'
> > drivers/built-in.o: In function `msi_init':
> > msi-laptop.c:(.init.text+0xe055): undefined reference to `sparse_keymap_setup'
> > msi-laptop.c:(.init.text+0xe07d): undefined reference to `sparse_keymap_free'
> > 
> 
> Either a missing CONFIG_INPUT_SPARSEKMAP dependency, or missing stubs in
> include/linux/input/sparse-keymap.h?
> 

No, stubs for sparse keymap do not make sense (either one wants to use
this library-like module or she does not), so it must be the missing
"select" (sparse keymap should be selectable as long as selecting module
depends on CONFIG_INPUT).

Thanks.

-- 
Dmitry

  reply	other threads:[~2011-04-12  5:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-12  4:18 undefined reference to `sparse_keymap_free' Steve French
2011-04-12  5:48 ` Andrew Morton
2011-04-12  5:58   ` Dmitry Torokhov [this message]
2011-04-12  6:33     ` Joey Lee

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=20110412055851.GA1854@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=joeyli.kernel@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg@redhat.com \
    --cc=smfrench@gmail.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