From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: input-current tree build failure
Date: Thu, 17 Sep 2009 23:02:52 -0700 [thread overview]
Message-ID: <20090918060252.GD18668@core.coreip.homeip.net> (raw)
In-Reply-To: <20090917111228.800851b0.sfr@canb.auug.org.au>
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
prev parent reply other threads:[~2009-09-18 6:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 1:12 linux-next: input-current tree build failure Stephen Rothwell
2009-09-18 6:02 ` Dmitry Torokhov [this message]
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=20090918060252.GD18668@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).