linux-kernel - Re: linux-next: Tree for Oct 31 (input & leds)

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: <52729BCB.1000700@infradead.org>
Date:	Thu, 31 Oct 2013 11:04:59 -0700
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,
	Samuel Thibault <samuel.thibault@...-lyon.org>
Subject: Re: linux-next: Tree for Oct 31 (input & leds)

On 10/31/13 03:00, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20131030:
> 
> The net-next tree gained a conflict against the net tree.
> 
> The devicetree tree gained a conflict against the crypto tree.
> 
> The tty tree gained a build failure so I used the version from
> next-20131030.
> 
> The arm-soc tree gained conflicts against the devicetree tree.


on i386, when both
CONFIG_INPUT=m
CONFIG_INPUT_LEDS=m

ERROR: "input_led_disconnect" [drivers/input/input-core.ko] undefined!
ERROR: "input_led_connect" [drivers/input/input-core.ko] undefined!


Full randconfig file is attached.


-- 
~Randy

View attachment "config-r5081" of type "text/plain" (85504 bytes)