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: build failure after merge of the final tree (input tree related)
Date: Tue, 23 Mar 2010 00:31:10 -0700 [thread overview]
Message-ID: <20100323073110.GA2157@core.coreip.homeip.net> (raw)
In-Reply-To: <20100323175456.e01dd822.sfr@canb.auug.org.au>
On Tue, Mar 23, 2010 at 05:54:56PM +1100, Stephen Rothwell wrote:
> Hi Dmitry,
>
> After merging the final tree, today's linux-next build (powerpc
> ppc44x_defconfig) failed like this:
>
> drivers/built-in.o: In function `sysrq_filter':
> sysrq.c:(.text+0x224da): undefined reference to `fg_console'
> sysrq.c:(.text+0x224e2): undefined reference to `fg_console'
> sysrq.c:(.text+0x224f2): undefined reference to `vc_cons'
> sysrq.c:(.text+0x224f6): undefined reference to `vc_cons'
> drivers/built-in.o: In function `sysrq_disconnect':
> sysrq.c:(.text+0x226e4): undefined reference to `input_close_device'
> sysrq.c:(.text+0x226ec): undefined reference to `input_unregister_handle'
> drivers/built-in.o: In function `sysrq_connect':
> sysrq.c:(.text+0x22780): undefined reference to `input_register_handle'
> sysrq.c:(.text+0x22790): undefined reference to `input_open_device'
> sysrq.c:(.text+0x227f0): undefined reference to `input_unregister_handle'
> drivers/built-in.o: In function `sysrq_toggle_support':
> (.text+0x22b6c): undefined reference to `input_unregister_handler'
> drivers/built-in.o: In function `sysrq_toggle_support':
> (.text+0x22bac): undefined reference to `input_register_handler'
> drivers/built-in.o: In function `sysrq_init':
> sysrq.c:(.init.text+0x18d4): undefined reference to `input_register_handler'
>
> Caused by commit edc6e384f9d96e54a6d03068d3b03fa5b56b6449 ("Input:
> implement SysRq as a separate input handler"). This build does not have
> CONFIG_HW_CONSOLE or CONFIG_INPUT set, but does have CONFIG_MAGIC_SYSRQ
> set to 'y'.
>
Sorry about this, I did not expect Sysrq being available without input.
I will try to fix up the tree in time for your tomorrow fetch.
--
Dmitry
next prev parent reply other threads:[~2010-03-23 7:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 6:54 linux-next: build failure after merge of the final tree (input tree related) Stephen Rothwell
2010-03-23 7:31 ` Dmitry Torokhov [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-20 3:12 Stephen Rothwell
2010-08-21 7:39 ` Dmitry Torokhov
2010-12-29 1:51 Stephen Rothwell
2010-12-29 2:34 ` Dmitry Torokhov
2010-12-29 23:51 ` Stephen Rothwell
2010-12-30 18:06 ` Ping Cheng
2010-12-30 19:58 ` Geert Uytterhoeven
2010-12-30 20:10 ` Ping Cheng
2011-01-02 8:05 ` Dmitry Torokhov
2011-09-19 8:46 Stephen Rothwell
2011-09-19 9:01 ` Tobias Klauser
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=20100323073110.GA2157@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).