linux-kernel - Re: linux-next: input-current tree build failure

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] [day] [month] [year] [list]

Message-ID: <20090918060252.GD18668@core.coreip.homeip.net>
Date:	Thu, 17 Sep 2009 23:02:52 -0700
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: input-current tree build failure

Hi Stephen,

On Thu, Sep 17, 2009 at 11:12:28AM +1000, Stephen Rothwell wrote:
> Hi Dmitry,
> 
> Today's linux-next build (x86_64 allmodconfig) failed like this:
> 
> In file included from drivers/input/serio/i8042.c:23:
> include/linux/i8042.h: In function 'i8042_check_port_owner':
> include/linux/i8042.h:58: error: parameter name omitted
> drivers/input/serio/i8042.c: At top level:
> drivers/input/serio/i8042.c:130: error: redefinition of 'i8042_lock_chip'
> include/linux/i8042.h:45: note: previous definition of 'i8042_lock_chip' was here
> drivers/input/serio/i8042.c:136: error: redefinition of 'i8042_unlock_chip'
> include/linux/i8042.h:49: note: previous definition of 'i8042_unlock_chip' was here
> drivers/input/serio/i8042.c:246: error: redefinition of 'i8042_command'
> include/linux/i8042.h:53: note: previous definition of 'i8042_command' was here
> drivers/input/serio/i8042.c:1193: error: redefinition of 'i8042_check_port_owner'
> include/linux/i8042.h:58: note: previous definition of 'i8042_check_port_owner' was here
> 
> Caused by commit 1f57f19e6245c5534c3518a8455419461ec06778 ("Input: libps2
> - additional locking for i8042 ports").
> 
> Please, if you add code that depends on a CONFIG option, build it with
> and without the options set ...
> 

I did ;) ... but not as module, sorry about this, will fix in a moment.

-- 
Dmitry
--
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/