From: Manikanta Maddireddy <mmaddireddy@nvidia.com>
To: <thierry.reding@gmail.com>, <jonathanh@nvidia.com>,
<robh+dt@kernel.org>, <frowand.list@gmail.com>,
<bhelgaas@google.com>, <rjw@rjwysocki.net>, <tglx@linutronix.de>
Cc: <vidyas@nvidia.com>, <kthota@nvidia.com>,
<linux-tegra@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-pci@vger.kernel.org>, <linux-pm@vger.kernel.org>,
Manikanta Maddireddy <mmaddireddy@nvidia.com>
Subject: [PATCH 01/10] genirq: Export irq_set_msi_desc()
Date: Fri, 24 Nov 2017 21:23:11 +0530 [thread overview]
Message-ID: <1511538800-8275-2-git-send-email-mmaddireddy@nvidia.com> (raw)
In-Reply-To: <1511538800-8275-1-git-send-email-mmaddireddy@nvidia.com>
PCI bus support MSI interrupts, allow PCI host driver to set MSI descriptor
data for an irq.
Signed-off-by: Manikanta Maddireddy <mmaddireddy@nvidia.com>
---
kernel/irq/chip.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/irq/chip.c b/kernel/irq/chip.c
index 5a2ef92c2782..bfbd17386bc4 100644
--- a/kernel/irq/chip.c
+++ b/kernel/irq/chip.c
@@ -136,6 +136,7 @@ int irq_set_msi_desc(unsigned int irq, struct msi_desc *entry)
{
return irq_set_msi_desc_off(irq, 0, entry);
}
+EXPORT_SYMBOL(irq_set_msi_desc);
/**
* irq_set_chip_data - set irq chip data for an irq
--
2.1.4
next prev parent reply other threads:[~2017-11-24 15:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 15:53 [PATCH 00/10] Add loadable kernel module and power management support Manikanta Maddireddy
2017-11-24 15:53 ` Manikanta Maddireddy [this message]
2017-11-24 23:55 ` [PATCH 01/10] genirq: Export irq_set_msi_desc() Thomas Gleixner
2017-11-25 19:41 ` Manikanta Maddireddy
2017-11-28 10:00 ` Marc Zyngier
2017-11-28 17:19 ` Manikanta Maddireddy
2017-11-24 15:53 ` [PATCH 02/10] of: Export of_pci_range_to_resource() Manikanta Maddireddy
2017-11-24 15:53 ` [PATCH 03/10] PM / QoS: Fix device resume latency for non PM QoS devices Manikanta Maddireddy
2017-11-24 16:50 ` Rafael J. Wysocki
2017-11-24 20:39 ` Thierry Reding
2017-11-25 0:02 ` Rafael J. Wysocki
2017-11-25 19:46 ` Manikanta Maddireddy
2017-11-24 15:53 ` [PATCH 04/10] ARM: tegra: EXPORT tegra_cpuidle_pcie_irqs_in_use() Manikanta Maddireddy
2017-11-30 12:41 ` Lorenzo Pieralisi
2017-11-30 18:46 ` Manikanta Maddireddy
2017-11-24 15:53 ` [PATCH 05/10] PCI: Export pci_find_host_bridge() Manikanta Maddireddy
2017-11-24 15:53 ` [PATCH 06/10] PCI: Export pci_flags Manikanta Maddireddy
2017-11-24 15:53 ` [PATCH 07/10] PCI: tegra: free resources on probe failure Manikanta Maddireddy
2017-11-24 15:53 ` [PATCH 08/10] PCI: tegra: Add loadable kernel module support Manikanta Maddireddy
2017-11-24 15:53 ` [PATCH 09/10] PCI: tegra: Broadcast PME_turn_Off message before link goes to L2 Manikanta Maddireddy
2017-11-24 15:53 ` [PATCH 10/10] PCI: tegra: Add power management support Manikanta Maddireddy
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=1511538800-8275-2-git-send-email-mmaddireddy@nvidia.com \
--to=mmaddireddy@nvidia.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=kthota@nvidia.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
--cc=vidyas@nvidia.com \
/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).