From: Balaji Rao <balajirrao@openmoko.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Samuel Ortiz <sameo@openedhand.com>, linux-next@vger.kernel.org
Subject: Re: linux-next: mfd tree build failure
Date: Mon, 12 Jan 2009 15:37:55 +0530 [thread overview]
Message-ID: <20090112100753.GA21301@fedora.yogi> (raw)
In-Reply-To: <20090112140318.e25cd2bf.sfr@canb.auug.org.au>
On Mon, Jan 12, 2009 at 02:03:18PM +1100, Stephen Rothwell wrote:
> Hi Samuel,
>
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> ERROR: "__set_irq_handler" [drivers/mfd/pcf50633-core.ko] undefined!
> ERROR: "handle_level_irq" [drivers/mfd/pcf50633-core.ko] undefined!
>
> Immediate cause is clearly commit
> f52046b14b1e1a8a02ae48d0c69d39c5e204644f ("mfd: PCF50633 core driver")
> which introduces this code. The above functions don't appear to be
> exported to modules.
>
> I have dropped the mfd tree for today.
Oh, sorry about this. I can actually do without this. Here's the patch.
Sameo, can you please apply it ?
pcf50633: Remove references to non-exported functions
Remove references to set_irq_type and handle_level_irq which are not
exported to modules.
Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
diff --git a/drivers/mfd/pcf50633-core.c b/drivers/mfd/pcf50633-core.c
index 24508e2..ea9488e 100644
--- a/drivers/mfd/pcf50633-core.c
+++ b/drivers/mfd/pcf50633-core.c
@@ -626,7 +626,6 @@ static int __devinit pcf50633_probe(struct i2c_client *client,
}
if (client->irq) {
- set_irq_handler(client->irq, handle_level_irq);
ret = request_irq(client->irq, pcf50633_irq,
IRQF_TRIGGER_LOW, "pcf50633", pcf);
next prev parent reply other threads:[~2009-01-12 10:08 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 3:03 linux-next: mfd tree build failure Stephen Rothwell
2009-01-12 10:07 ` Balaji Rao [this message]
2009-01-13 6:24 ` Stephen Rothwell
2009-01-14 12:12 ` Samuel Ortiz
-- strict thread matches above, loose matches on Subject: below --
2010-01-19 4:06 Stephen Rothwell
2010-01-19 10:59 ` Samuel Ortiz
2010-01-19 11:34 ` Stephen Rothwell
2010-01-11 5:02 Stephen Rothwell
2010-01-11 10:51 ` Mark Brown
2010-01-11 12:02 ` Haojian Zhuang
2010-01-11 12:33 ` Samuel Ortiz
2010-01-11 22:44 ` Stephen Rothwell
2009-11-24 5:37 Stephen Rothwell
2009-11-24 9:57 ` Mark Brown
2009-11-24 10:14 ` Stephen Rothwell
2009-11-24 10:40 ` Mark Brown
2009-11-23 3:41 Stephen Rothwell
2009-11-23 4:03 ` Stephen Rothwell
2009-11-23 12:29 ` Samuel Ortiz
2009-11-23 13:11 ` Mark Brown
2009-11-23 14:44 ` Samuel Ortiz
2009-11-23 15:20 ` Mark Brown
2009-11-23 3:35 Stephen Rothwell
2009-11-23 12:26 ` Samuel Ortiz
2009-11-23 16:32 ` Dmitry Torokhov
2009-11-24 23:35 ` Samuel Ortiz
2009-10-06 2:02 Stephen Rothwell
2009-10-06 2:35 ` Haojian Zhuang
2009-10-06 2:35 ` Haojian Zhuang
2009-10-06 3:54 ` Stephen Rothwell
2009-10-06 4:19 ` Haojian Zhuang
2009-10-08 5:59 ` Haojian Zhuang
2009-10-08 5:59 ` Haojian Zhuang
2009-10-12 2:11 ` Stephen Rothwell
2008-08-05 14:08 Stephen Rothwell
2008-08-05 15:39 ` ian
2008-08-05 16:05 ` Adrian Bunk
2008-08-05 18:50 ` ian
2008-08-05 16:05 ` Stephen Rothwell
2008-08-05 16:08 ` Samuel Ortiz
2008-08-05 16:16 ` Stephen Rothwell
2008-08-05 17:40 ` Samuel Ortiz
2008-08-05 18:46 ` ian
2008-08-06 9:53 ` Samuel Ortiz
2008-08-06 0:40 ` Stephen Rothwell
2008-08-05 5:09 Stephen Rothwell
2008-08-05 13:03 ` ian
2008-08-05 13:09 ` Samuel Ortiz
2008-08-05 13:22 ` Stephen Rothwell
2008-08-05 15:29 ` ian
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=20090112100753.GA21301@fedora.yogi \
--to=balajirrao@openmoko.org \
--cc=linux-next@vger.kernel.org \
--cc=sameo@openedhand.com \
--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.