From: Dmitry Torokhov <dmitry.torokhov@gmail•com>
To: Randy Dunlap <randy.dunlap@oracle•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: input tree build failure
Date: Mon, 7 Dec 2009 09:36:41 -0800 [thread overview]
Message-ID: <20091207173640.GA998@core.coreip.homeip.net> (raw)
In-Reply-To: <4B1D2C80.4060202@oracle.com>
On Mon, Dec 07, 2009 at 08:25:36AM -0800, Randy Dunlap wrote:
> Stephen Rothwell wrote:
> > Hi Dmitry,
> >
> > Today's linux-next build (powerpc allyesconfig) failed like this:
> >
> > drivers/input/sparse-keymap.c:101: error: __ksymtab_sparse_keymap_setkeycode causes a section type conflict
> >
> > Caused by commit a2dd9f7ceeb28f495587834aa5778c721611d61b ("Input: add
> > generic support for sparse keymaps").
> >
> > static functions should not given to EXPORT_SYMBOL().
> >
> > I have reverted that commit for today.
>
> (DT:) Is that what causes wistron_btns builds to fail also?
>
Umm... Wistron and dm355evm_keys now using sparse keymap library so if
it is missing they would fail to compile.
I removed the stray EXPORT_SYMBOL(), shold be good now.
--
Dmitry
next prev parent reply other threads:[~2009-12-07 17:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 9:03 linux-next: input tree build failure Stephen Rothwell
2009-12-07 16:25 ` Randy Dunlap
2009-12-07 17:36 ` Dmitry Torokhov [this message]
2009-12-07 22:16 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2010-01-25 5:52 Stephen Rothwell
2010-01-25 6:46 ` Dmitry Torokhov
2010-01-25 7:26 ` Tobias Klauser
2009-03-10 4:49 Stephen Rothwell
2009-03-10 5:02 ` Dmitry Torokhov
2009-03-10 5:14 ` Stephen Rothwell
2008-08-19 6:31 Stephen Rothwell
2008-08-19 13:01 ` Dmitry Torokhov
2008-08-19 19:59 ` Greg KH
2008-08-19 20:00 ` Greg KH
2008-08-20 5:49 ` Stephen Rothwell
2008-08-20 18:35 ` Greg KH
2008-08-22 20:29 ` Dmitry Torokhov
2008-08-22 22:15 ` Alfred E. Heggestad
2008-08-25 0:01 ` Stephen Rothwell
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=20091207173640.GA998@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=randy.dunlap@oracle$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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