From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760596AbcBYKCY (ORCPT ); Thu, 25 Feb 2016 05:02:24 -0500 Received: from torg.zytor.com ([198.137.202.12]:34526 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1760390AbcBYKCD (ORCPT ); Thu, 25 Feb 2016 05:02:03 -0500 Date: Thu, 25 Feb 2016 02:01:35 -0800 From: tip-bot for Qais Yousef Message-ID: Cc: linux-mips@linux-mips.org, marc.zyngier@arm.com, hpa@zytor.com, linux-kernel@vger.kernel.org, ralf@linux-mips.org, jiang.liu@linux.intel.com, jason@lakedaemon.net, tglx@linutronix.de, qais.yousef@imgtec.com, lisa.parratt@imgtec.com, qsyousef@gmail.com, mingo@kernel.org Reply-To: qsyousef@gmail.com, mingo@kernel.org, lisa.parratt@imgtec.com, tglx@linutronix.de, qais.yousef@imgtec.com, marc.zyngier@arm.com, linux-mips@linux-mips.org, hpa@zytor.com, linux-kernel@vger.kernel.org, jiang.liu@linux.intel.com, ralf@linux-mips.org, jason@lakedaemon.net In-Reply-To: <1449580830-23652-7-git-send-email-qais.yousef@imgtec.com> References: <1449580830-23652-7-git-send-email-qais.yousef@imgtec.com> To: linux-tip-commits@vger.kernel.org Subject: [tip:irq/core] genirq: Add an extra comment about the use of affinity in irq_common_data Git-Commit-ID: 955bfe5912e7839abcc83694f06867535487404b X-Mailer: tip-git-log-daemon Robot-ID: Robot-Unsubscribe: Contact to get blacklisted from these emails MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Commit-ID: 955bfe5912e7839abcc83694f06867535487404b Gitweb: http://git.kernel.org/tip/955bfe5912e7839abcc83694f06867535487404b Author: Qais Yousef AuthorDate: Tue, 8 Dec 2015 13:20:17 +0000 Committer: Thomas Gleixner CommitDate: Thu, 25 Feb 2016 10:56:55 +0100 genirq: Add an extra comment about the use of affinity in irq_common_data Affinity will have dual meaning depends on the type of the irq. If it is a normal irq, it'll have the standard affinity meaning. If it is an IPI, it will hold the mask of the cpus to which an IPI can be sent. Signed-off-by: Qais Yousef Cc: Cc: Cc: Cc: Cc: Cc: Cc: Qais Yousef Link: http://lkml.kernel.org/r/1449580830-23652-7-git-send-email-qais.yousef@imgtec.com Signed-off-by: Thomas Gleixner --- include/linux/irq.h | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/include/linux/irq.h b/include/linux/irq.h index 3c1c967..0817afd 100644 --- a/include/linux/irq.h +++ b/include/linux/irq.h @@ -133,7 +133,9 @@ struct irq_domain; * Use accessor functions to deal with it * @node: node index useful for balancing * @handler_data: per-IRQ data for the irq_chip methods - * @affinity: IRQ affinity on SMP + * @affinity: IRQ affinity on SMP. If this is an IPI + * related irq, then this is the mask of the + * CPUs to which an IPI can be sent. * @msi_desc: MSI descriptor */ struct irq_common_data {