It's easier to accept the name of msi_chip_set_affinity() than msi_domain_set_affinity(), since function of setting interrupt affinity is actually provided by IRQ chips.
Signed-off-by: Yun Wu <[email protected]> --- include/linux/msi.h | 4 ++-- kernel/irq/msi.c | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/include/linux/msi.h b/include/linux/msi.h index 8ac4a68..c099e6c 100644 --- a/include/linux/msi.h +++ b/include/linux/msi.h @@ -210,8 +210,8 @@ enum { MSI_FLAG_PCI_MSIX = (1 << 4), }; -int msi_domain_set_affinity(struct irq_data *data, const struct cpumask *mask, - bool force); +int msi_chip_set_affinity(struct irq_data *data, const struct cpumask *mask, + bool force); struct irq_domain *msi_create_irq_domain(struct device_node *of_node, struct msi_domain_info *info, diff --git a/kernel/irq/msi.c b/kernel/irq/msi.c index b773708..3261480 100644 --- a/kernel/irq/msi.c +++ b/kernel/irq/msi.c @@ -39,7 +39,7 @@ static inline void irq_chip_write_msi_msg(struct irq_data *data, } /** - * msi_domain_set_affinity - Generic affinity setter function for MSI domains + * msi_chip_set_affinity - Generic affinity setter function for MSI domains * @irq_data: The irq data associated to the interrupt * @mask: The affinity mask to set * @force: Flag to enforce setting (disable online checks) @@ -47,7 +47,7 @@ static inline void irq_chip_write_msi_msg(struct irq_data *data, * Intended to be used by MSI interrupt controllers which are * implemented with hierarchical domains. */ -int msi_domain_set_affinity(struct irq_data *irq_data, +int msi_chip_set_affinity(struct irq_data *irq_data, const struct cpumask *mask, bool force) { struct msi_msg msg; @@ -216,7 +216,7 @@ static void msi_domain_update_chip_ops(struct msi_domain_info *info) if (!chip->irq_unmask) chip->irq_unmask = pci_msi_unmask_irq; if (!chip->irq_set_affinity) - chip->irq_set_affinity = msi_domain_set_affinity; + chip->irq_set_affinity = msi_chip_set_affinity; } /** -- 1.8.0 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
