From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/6] genirq: export percpu irq functions for module usage
Date: Fri, 1 Nov 2013 09:31:52 -0700 [thread overview]
Message-ID: <1383323516-31357-3-git-send-email-sboyd@codeaurora.org> (raw)
In-Reply-To: <1383323516-31357-1-git-send-email-sboyd@codeaurora.org>
In the near future we're going to use these percpu irq functions
in the Krait CPU EDAC driver. Export them so that the EDAC driver
can be compiled as a module.
Acked-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
---
kernel/irq/manage.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
index 514bcfd..c6009d1 100644
--- a/kernel/irq/manage.c
+++ b/kernel/irq/manage.c
@@ -1623,6 +1623,7 @@ void free_percpu_irq(unsigned int irq, void __percpu *dev_id)
kfree(__free_percpu_irq(irq, dev_id));
chip_bus_sync_unlock(desc);
}
+EXPORT_SYMBOL_GPL(free_percpu_irq);
/**
* setup_percpu_irq - setup a per-cpu interrupt
@@ -1693,3 +1694,4 @@ int request_percpu_irq(unsigned int irq, irq_handler_t handler,
return retval;
}
+EXPORT_SYMBOL_GPL(request_percpu_irq);
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2013-11-01 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 16:31 [PATCH v3 0/6] Krait L1/L2 EDAC driver Stephen Boyd
2013-11-01 16:31 ` [PATCH v3 1/6] edac: Don't try to cancel workqueue when it's never setup Stephen Boyd
2013-11-01 16:31 ` Stephen Boyd [this message]
2013-11-01 16:31 ` [PATCH v3 3/6] ARM: Add Krait L2 accessor functions Stephen Boyd
2013-11-01 16:31 ` [PATCH v3 4/6] edac: Document Krait L1/L2 EDAC driver binding Stephen Boyd
2013-11-01 16:31 ` [PATCH v3 5/6] edac: Add support for Krait CPU cache error detection Stephen Boyd
2013-11-01 16:31 ` [PATCH v3 6/6] ARM: dts: msm: Add Krait CPU/L2 nodes Stephen Boyd
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=1383323516-31357-3-git-send-email-sboyd@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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).