linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Keith Busch <keith.busch@intel.com>
To: LKML <linux-kernel@vger.kernel.org>,
	x86@kernel.org, linux-pci@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Bjorn Helgaas <bhelgaas@google.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
	Bryan Veal <bryan.e.veal@intel.com>,
	Jon Derrick <jonathan.derrick@intel.com>,
	Keith Busch <keith.busch@intel.com>
Subject: [PATCHv8 2/5] x86/IRQ: Export IRQ domain function for module use
Date: Tue, 12 Jan 2016 13:18:07 -0700	[thread overview]
Message-ID: <1452629890-17542-3-git-send-email-keith.busch@intel.com> (raw)
In-Reply-To: <1452629890-17542-1-git-send-email-keith.busch@intel.com>

Signed-off-by: Keith Busch <keith.busch@intel.com>
---
 kernel/irq/irqdomain.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/kernel/irq/irqdomain.c b/kernel/irq/irqdomain.c
index 8cf95de..6e655f7 100644
--- a/kernel/irq/irqdomain.c
+++ b/kernel/irq/irqdomain.c
@@ -1061,6 +1061,7 @@ void irq_domain_set_info(struct irq_domain *domain, unsigned int virq,
 	__irq_set_handler(virq, handler, 0, handler_name);
 	irq_set_handler_data(virq, handler_data);
 }
+EXPORT_SYMBOL(irq_domain_set_info);
 
 /**
  * irq_domain_reset_irq_data - Clear hwirq, chip and chip_data in @irq_data
-- 
2.6.2.307.g37023ba


  parent reply	other threads:[~2016-01-12 20:18 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-12 20:18 [PATCHv8 0/5] Driver for new "VMD" device Keith Busch
2016-01-12 20:18 ` [PATCHv8 1/5] msi: Relax msi_domain_alloc() to support parentless MSI irqdomains Keith Busch
2016-01-12 20:18 ` Keith Busch [this message]
2016-01-12 20:18 ` [PATCHv8 3/5] x86/PCI: Allow PCI domain specific dma ops Keith Busch
2016-01-12 20:18 ` [PATCHv8 4/5] PCI/AER: Use 32 bit int type domains Keith Busch
2016-01-12 20:18 ` [PATCHv8 5/5] x86/PCI: Initial commit for new VMD device driver Keith Busch
2016-01-15 18:19 ` [PATCHv8 0/5] Driver for new "VMD" device Bjorn Helgaas
2016-01-15 19:31   ` Veal, Bryan E.
2016-01-15 21:49     ` Bjorn Helgaas
2016-01-16 22:19       ` Veal, Bryan E.
2016-01-20 22:01         ` Bjorn Helgaas
2016-02-22 22:10           ` Bjorn Helgaas
2016-02-23 18:24             ` Keith Busch
2016-02-25 14:42               ` Bjorn Helgaas
2016-02-25 14:50                 ` Keith Busch
2016-02-26 15:29                 ` Keith Busch
2016-01-15 19:32   ` Keith Busch
2016-01-15 19:44   ` Thomas Gleixner
2016-01-15 20:03     ` Bjorn Helgaas
2016-01-15 20:14       ` Thomas Gleixner
2016-01-15 19:48   ` Derrick, Jonathan
2016-01-15 19:54     ` Keith Busch
2016-01-15 20:02       ` Jon Derrick
2016-01-15 22:06     ` Bjorn Helgaas
2016-01-19 15:38       ` Keith Busch
2016-01-19 16:02         ` Christoph Hellwig
2016-01-19 16:36           ` Keith Busch
2016-01-19 22:05             ` Veal, Bryan E.
2016-01-20 20:43           ` Bjorn Helgaas
2016-01-26 16:46             ` Christoph Hellwig
2016-01-26 18:23               ` Veal, Bryan E.
2016-01-17 17:58 ` Christoph Hellwig

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=1452629890-17542-3-git-send-email-keith.busch@intel.com \
    --to=keith.busch@intel.com \
    --cc=bhelgaas@google.com \
    --cc=bryan.e.veal@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=jonathan.derrick@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@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;
as well as URLs for NNTP newsgroup(s).