linux-kernel - Re: linux-next: Tree for Nov 12 (staging/unisys/visorinput)

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: <5644F106.2030503@infradead.org>
Date:	Thu, 12 Nov 2015 12:05:26 -0800
From:	Randy Dunlap <rdunlap@...radead.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>, linux-next@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Ken Cox <jkc@...hat.com>, Ben Romer <sparmaintainer@...sys.com>
Subject: Re: linux-next: Tree for Nov 12 (staging/unisys/visorinput)

On 11/11/15 18:01, Stephen Rothwell wrote:
> Hi all,
> 
> Please do *not* add any material intended for v4.5 to your linux-next
> included branches until after v4.4-rc1 has been released.
> 
> Changes since 20151111:
> 
> *cickets*
   eh??

on x86_64:

ERROR: "input_event" [drivers/staging/unisys/visorinput/visorinput.ko] undefined!
ERROR: "input_set_capability" [drivers/staging/unisys/visorinput/visorinput.ko] undefined!
ERROR: "input_set_abs_params" [drivers/staging/unisys/visorinput/visorinput.ko] undefined!
ERROR: "input_free_device" [drivers/staging/unisys/visorinput/visorinput.ko] undefined!
ERROR: "input_register_device" [drivers/staging/unisys/visorinput/visorinput.ko] undefined!
ERROR: "input_allocate_device" [drivers/staging/unisys/visorinput/visorinput.ko] undefined!
ERROR: "input_unregister_device" [drivers/staging/unisys/visorinput/visorinput.ko] undefined!

when CONFIG_INPUT is not enabled.

Just add
	depends on INPUT
to this driver's Kconfig file.

Thanks.

-- 
~Randy
--
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/