linux-kernel - Re: [PATCH] wimax: fix compile bug

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1231434218.5298.19.camel@californication>
Date:	Thu, 08 Jan 2009 18:03:38 +0100
From:	Marcel Holtmann <marcel@...tmann.org>
To:	Heiko Carstens <heiko.carstens@...ibm.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Inaky Perez-Gonzalez <inaky@...ux.intel.com>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	Martin Schwidefsky <schwidefsky@...ibm.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] wimax: fix compile bug

Hi Heiko,

> wimax should depend on INPUT:
> 
> net/built-in.o: In function `wimax_rfkill_rm':
> linux-2.6/net/wimax/op-rfkill.c:428: undefined reference to `input_unregister_device'
> net/built-in.o: In function `wimax_rfkill_add':
> linux-2.6/net/wimax/op-rfkill.c:370: undefined reference to `input_allocate_device'
> linux-2.6/net/wimax/op-rfkill.c:384: undefined reference to `input_register_device'
> linux-2.6/net/wimax/op-rfkill.c:402: undefined reference to `input_unregister_device'
> linux-2.6/net/wimax/op-rfkill.c:406: undefined reference to `input_free_device'
> net/built-in.o: In function `input_report_key':
> linux-2.6/include/linux/input.h:1285: undefined reference to `input_event'
> 
> Cc: Inaky Perez-Gonzalez <inaky@...ux.intel.com>
> Cc: Greg Kroah-Hartman <gregkh@...e.de>
> Signed-off-by: Heiko Carstens <heiko.carstens@...ibm.com>

actually Inaky posted a different fix for this to netdev yesterday.

Regards

Marcel


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/