From: Balaji Rao <balajirrao@openmoko.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: David Miller <davem@redhat.com>,
linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org,
andy@openmoko.com, sameo@openedhand.com, mingo@elte.hu,
yinghai@kernel.org, akpm@linux-foundation.org,
sfr@canb.auug.org.au
Subject: Re: pcf50663 MFD driver modular build failure
Date: Thu, 15 Jan 2009 10:33:25 +0530 [thread overview]
Message-ID: <20090115050324.GA3199@fedora.yogi> (raw)
In-Reply-To: <20090114134712.6f0e430e.randy.dunlap@oracle.com>
On Wed, Jan 14, 2009 at 01:47:12PM -0800, Randy Dunlap wrote:
> On Tue, 13 Jan 2009 12:22:02 +0530 Balaji Rao wrote:
>
> > On Mon, Jan 12, 2009 at 09:05:01PM -0800, David Miller wrote:
> > >
> > > This started happening with Linus's pull from today for
> > > sparc64 allmodconfig:
> > >
> > > ERROR: "__set_irq_handler" [drivers/mfd/pcf50633-core.ko] undefined!
> > > ERROR: "handle_level_irq" [drivers/mfd/pcf50633-core.ko] undefined!
> > >
> > > Sure we can export __set_irq_handler() and handle_level_irq() to
> > > modules to fix this, but that looks like some hokey stuff for
> > > a MFD driver to be doing :-)
> >
> > Yes, right! It's really not necessary. I've sent a patch to remove it.
>
> Who did you send the patch to and where is it in the queue??
Samuel has taken it into his linux-mfd tree and should be sending a pull
request real soon.
Thanks,
Balaji
prev parent reply other threads:[~2009-01-15 5:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 5:05 pcf50663 MFD driver modular build failure David Miller
2009-01-13 6:52 ` Balaji Rao
2009-01-14 1:29 ` Kyle McMartin
2009-01-14 21:47 ` Randy Dunlap
2009-01-15 5:03 ` Balaji Rao [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=20090115050324.GA3199@fedora.yogi \
--to=balajirrao@openmoko.org \
--cc=akpm@linux-foundation.org \
--cc=andy@openmoko.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=randy.dunlap@oracle.com \
--cc=sameo@openedhand.com \
--cc=sfr@canb.auug.org.au \
--cc=sparclinux@vger.kernel.org \
--cc=yinghai@kernel.org \
/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