From: Thomas Gleixner <tglx@linutronix.de>
To: Jiri Kosina <jkosina@suse.cz>
Cc: "Paweł Sikora" <pluto@pld-linux.org>,
linux-kernel@vger.kernel.org,
"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: Linux-3.4-rc7 [build failure]
Date: Sun, 13 May 2012 17:16:30 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1205131648110.3231@ionos> (raw)
In-Reply-To: <alpine.LRH.2.00.1205131157290.22597@twin.jikos.cz>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2389 bytes --]
On Sun, 13 May 2012, Jiri Kosina wrote:
> On Sun, 13 May 2012, Paweł Sikora wrote:
>
> > Hi all,
> > i see a build failure on modular kernel.
> >
> > (...)
> > Kernel: arch/x86/boot/bzImage is ready (#15)
> > MODPOST 3501 modules
> > ERROR: "handle_edge_irq" [drivers/gpio/gpio-pch.ko] undefined!
> > ERROR: "irq_to_desc" [drivers/gpio/gpio-pch.ko] undefined!
> > WARNING: modpost: Found 4 section mismatch(es).
> > (...)
>
> This is caused by
>
> commit df9541a60af0985c3a756dc5f99b9253d2565a07
> Author: Thomas Gleixner <tglx@linutronix.de>
> Date: Sat Apr 28 10:13:45 2012 +0200
>
> gpio: pch9: Use proper flow type handlers
>
>
> as it adds
>
> __irq_set_handler_locked(d->irq, handle_edge_irq);
>
> but handle_edge_irq() is not exported for modules (and inlined
> __irq_set_handler_locked() requires irq_to_desc() exported as well)
>
> Thus the patch below fixes it; adding Thomas to CC to get his Ack for this
> first though.
Hrmpf. I'll take it via irg/urgent
>
>
> From: Jiri Kosina <jkosina@suse.cz>
> Subject: [PATCH] genirq: export handle_edge_irq() and irq_to_desc()
>
> Export handle_edge_irq() and irq_to_desc() to modules to allow them to
> do things such as
>
> __irq_set_handler_locked(...., handle_edge_irq);
>
> This fixes
>
> ERROR: "handle_edge_irq" [drivers/gpio/gpio-pch.ko] undefined!
> ERROR: "irq_to_desc" [drivers/gpio/gpio-pch.ko] undefined!
>
> when gpio-pch is being built as a module.
>
> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
> ---
> kernel/irq/chip.c | 1 +
> kernel/irq/irqdesc.c | 1 +
> 2 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/kernel/irq/chip.c b/kernel/irq/chip.c
> index 6080f6b..3914c1e 100644
> --- a/kernel/irq/chip.c
> +++ b/kernel/irq/chip.c
> @@ -518,6 +518,7 @@ handle_edge_irq(unsigned int irq, struct irq_desc *desc)
> out_unlock:
> raw_spin_unlock(&desc->lock);
> }
> +EXPORT_SYMBOL(handle_edge_irq);
>
> #ifdef CONFIG_IRQ_EDGE_EOI_HANDLER
> /**
> diff --git a/kernel/irq/irqdesc.c b/kernel/irq/irqdesc.c
> index d86e254..192a302 100644
> --- a/kernel/irq/irqdesc.c
> +++ b/kernel/irq/irqdesc.c
> @@ -112,6 +112,7 @@ struct irq_desc *irq_to_desc(unsigned int irq)
> {
> return radix_tree_lookup(&irq_desc_tree, irq);
> }
> +EXPORT_SYMBOL(irq_to_desc);
>
> static void delete_irq_desc(unsigned int irq)
> {
>
> --
> Jiri Kosina
> SUSE Labs
>
>
next prev parent reply other threads:[~2012-05-13 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-13 7:42 Linux-3.4-rc7 [build failure] Paweł Sikora
2012-05-13 10:13 ` Jiri Kosina
2012-05-13 15:16 ` Thomas Gleixner [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-05-13 16:02 Sedat Dilek
2012-05-13 20:50 ` joe
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=alpine.LFD.2.02.1205131648110.3231@ionos \
--to=tglx@linutronix.de \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=pluto@pld-linux.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).