All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
To: Randy Dunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	rt2400-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: next-20080611 rt2x00: build failure
Date: Wed, 11 Jun 2008 14:10:00 -0400	[thread overview]
Message-ID: <20080611181000.GA32331@tuxdriver.com> (raw)
In-Reply-To: <20080611100748.d35829f4.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>

On Wed, Jun 11, 2008 at 10:07:48AM -0700, Randy Dunlap wrote:
> when CONFIG_INPUT=n and
> # CONFIG_NEW_LEDS is not set
> CONFIG_LEDS_CLASS=y
> 
> (full config attached)
> 
> vmlinux.o: In function `iwl_rfkill_unregister':
> (.text+0x174cdc): undefined reference to `input_unregister_device'
> vmlinux.o: In function `iwl_rfkill_init':
> (.text+0x174d9f): undefined reference to `input_allocate_device'
> vmlinux.o: In function `iwl_rfkill_init':
> (.text+0x174e2d): undefined reference to `input_register_device'
> vmlinux.o: In function `iwl_rfkill_init':
> (.text+0x174e53): undefined reference to `input_free_device'
> vmlinux.o: In function `rt2x00rfkill_allocate_polldev':
> rt2x00rfkill.c:(.text+0x176dc4): undefined reference to `input_allocate_polled_device'
> vmlinux.o: In function `rt2x00rfkill_poll':
> rt2x00rfkill.c:(.text+0x176e8b): undefined reference to `input_event'
> rt2x00rfkill.c:(.text+0x176e9f): undefined reference to `input_event'

<snip>

Ick, what a mess...

So what combination of depends and select of INPUT, INPUT_POLLDEV,
and RFKILL_INPUT do we need to resolve this?

-- 
John W. Linville
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: "John W. Linville" <linville@tuxdriver.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-next@vger.kernel.org, linux-wireless@vger.kernel.org,
	rt2400-devel@lists.sourceforge.net
Subject: Re: next-20080611 rt2x00: build failure
Date: Wed, 11 Jun 2008 14:10:00 -0400	[thread overview]
Message-ID: <20080611181000.GA32331@tuxdriver.com> (raw)
In-Reply-To: <20080611100748.d35829f4.randy.dunlap@oracle.com>

On Wed, Jun 11, 2008 at 10:07:48AM -0700, Randy Dunlap wrote:
> when CONFIG_INPUT=n and
> # CONFIG_NEW_LEDS is not set
> CONFIG_LEDS_CLASS=y
> 
> (full config attached)
> 
> vmlinux.o: In function `iwl_rfkill_unregister':
> (.text+0x174cdc): undefined reference to `input_unregister_device'
> vmlinux.o: In function `iwl_rfkill_init':
> (.text+0x174d9f): undefined reference to `input_allocate_device'
> vmlinux.o: In function `iwl_rfkill_init':
> (.text+0x174e2d): undefined reference to `input_register_device'
> vmlinux.o: In function `iwl_rfkill_init':
> (.text+0x174e53): undefined reference to `input_free_device'
> vmlinux.o: In function `rt2x00rfkill_allocate_polldev':
> rt2x00rfkill.c:(.text+0x176dc4): undefined reference to `input_allocate_polled_device'
> vmlinux.o: In function `rt2x00rfkill_poll':
> rt2x00rfkill.c:(.text+0x176e8b): undefined reference to `input_event'
> rt2x00rfkill.c:(.text+0x176e9f): undefined reference to `input_event'

<snip>

Ick, what a mess...

So what combination of depends and select of INPUT, INPUT_POLLDEV,
and RFKILL_INPUT do we need to resolve this?

-- 
John W. Linville
linville@tuxdriver.com

  parent reply	other threads:[~2008-06-11 18:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-11 17:07 next-20080611 rt2x00: build failure Randy Dunlap
2008-06-11 17:48 ` [Rt2400-devel] " Ivo van Doorn
2008-06-11 17:46   ` Randy Dunlap
     [not found]     ` <32664704.1213206386295.JavaMail.oracle-s5rVz5nKm9nKpDp+h9PlwkEOCMrvLtNR@public.gmane.org>
2008-06-11 18:21       ` Ivo van Doorn
2008-06-11 18:21         ` Ivo van Doorn
     [not found] ` <20080611100748.d35829f4.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2008-06-11 18:10   ` John W. Linville [this message]
2008-06-11 18:10     ` John W. Linville
2008-06-11 19:03     ` [Rt2400-devel] " Ivo van Doorn
2008-06-11 19:32       ` Randy Dunlap
     [not found]         ` <20080611123245.4089f47b.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2008-06-11 19:59           ` Ivo van Doorn
2008-06-11 19:59             ` Ivo van Doorn
     [not found]             ` <200806112159.00779.IvDoorn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-06-11 19:57               ` [PATCH] " Randy Dunlap
2008-06-11 19:57                 ` Randy Dunlap
2008-06-11 20:32               ` [PATCH] next-20080611 rt2x00: LEDS " Randy Dunlap
2008-06-11 20:32                 ` Randy Dunlap
2008-06-11 22:15                 ` Ivo van Doorn

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=20080611181000.GA32331@tuxdriver.com \
    --to=linville-2xusbdqka4r54taoqtywwq@public.gmane.org \
    --cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
    --cc=rt2400-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /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.