From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Jorge Eduardo Candelaria <jedu@slimlogic.co.uk>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Graeme Gregory <gg@slimlogic.co.uk>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: linux-next: build failure after merge of the voltage tree
Date: Tue, 10 May 2011 09:38:32 +0100 [thread overview]
Message-ID: <1305016712.3206.2.camel@odin> (raw)
In-Reply-To: <20110510124434.b30a7631.sfr@canb.auug.org.au>
On Tue, 2011-05-10 at 12:44 +1000, Stephen Rothwell wrote:
> Hi Liam,
>
> After merging the voltage tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> ERROR: "tps65910_gpio_init" [drivers/mfd/tps65910.ko] undefined!
> ERROR: "tps65910_irq_init" [drivers/mfd/tps65910.ko] undefined!
> ERROR: "irq_modify_status" [drivers/mfd/tps65910-irq.ko] undefined!
> ERROR: "irq_set_chip_and_handler_name" [drivers/mfd/tps65910-irq.ko] undefined!
> ERROR: "handle_edge_irq" [drivers/mfd/tps65910-irq.ko] undefined!
>
> I have used the voltage tree from next-20110509 for today.
Jorge, could you send a fix for this today.
Thanks
Liam
next prev parent reply other threads:[~2011-05-10 8:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 2:44 linux-next: build failure after merge of the voltage tree Stephen Rothwell
2011-05-10 8:38 ` Liam Girdwood [this message]
2011-05-10 17:30 ` Jorge Eduardo Candelaria
2011-05-10 19:57 ` Liam Girdwood
2011-05-11 2:27 ` Stephen Rothwell
2011-05-11 6:43 ` Jorge Eduardo Candelaria
2011-05-11 13:29 ` Liam Girdwood
2011-05-11 8:47 ` [PATCH] mfd: TPS65910 depends on I2C and must be built in Mark Brown
2011-05-11 13:35 ` Liam Girdwood
2011-05-11 13:36 ` Mark Brown
[not found] <201105271759.p4RHxa2X008919@hera.kernel.org>
2011-05-27 19:58 ` linux-next: build failure after merge of the voltage tree Randy Dunlap
2011-05-27 21:13 ` Liam Girdwood
2011-05-27 21:21 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2010-12-15 2:09 Stephen Rothwell
2010-12-15 9:04 ` Liam Girdwood
2010-12-15 14:03 ` Mark Brown
2010-12-14 4:49 Stephen Rothwell
2010-12-14 5:10 ` Yong Shen
2010-12-14 15:56 ` Liam Girdwood
2010-12-15 2:03 ` Yong Shen
2010-11-11 0:36 Stephen Rothwell
2010-11-11 11:46 ` Mark Brown
2010-11-11 12:09 ` Liam Girdwood
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=1305016712.3206.2.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=gg@slimlogic.co.uk \
--cc=jedu@slimlogic.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.