From: David Miller <davem@davemloft.net>
To: jiang.liu@linux.intel.com
Cc: bhelgaas@google.com, tglx@linutronix.de, mingo@redhat.com,
grant.likely@linaro.org, marc.zyngier@arm.com,
stuart.yoder@freescale.com, wangyijing@huawei.com, bp@alien8.de,
eric.snowberg@oracle.com, tony.luck@intel.com,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, sparclinux@vger.kernel.org
Subject: Re: [RFC Patch V1 07/12] sparc, PCI: Use helper functions to access fields in struct msi_desc
Date: Thu, 09 Jul 2015 01:00:45 -0700 (PDT) [thread overview]
Message-ID: <20150709.010045.1327001449508270216.davem@davemloft.net> (raw)
In-Reply-To: <1436428847-8886-8-git-send-email-jiang.liu@linux.intel.com>
From: Jiang Liu <jiang.liu@linux.intel.com>
Date: Thu, 9 Jul 2015 16:00:42 +0800
> Use helper functions to access fields in struct msi_desc, so we could
> easily refine struct msi_desc later.
>
> Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
Acked-by: David S. Miller <davem@davemloft.net>
next prev parent reply other threads:[~2015-07-09 8:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 8:00 [RFC Patch V1 00/12] Reorganize struct msi_desc to prepare for support of generic MSI Jiang Liu
2015-07-09 8:00 ` [RFC Patch V1 01/12] PCI: Add helper function msi_desc_to_pci_sysdata() Jiang Liu
2015-07-09 8:00 ` [RFC Patch V1 02/12] MIPS, PCI: Use for_pci_msi_entry() to access MSI device list Jiang Liu
2015-07-09 11:03 ` Sergei Shtylyov
2015-07-09 8:00 ` [RFC Patch V1 03/12] PowerPC, " Jiang Liu
2015-07-09 8:00 ` [RFC Patch V1 04/12] s390/pci: " Jiang Liu
2015-07-13 12:47 ` Sebastian Ott
2015-07-09 8:00 ` [RFC Patch V1 05/12] x86, PCI: " Jiang Liu
2015-07-09 19:07 ` Konrad Rzeszutek Wilk
2015-07-09 8:00 ` [RFC Patch V1 06/12] " Jiang Liu
2015-07-09 19:08 ` Konrad Rzeszutek Wilk
2015-07-09 8:00 ` [RFC Patch V1 07/12] sparc, PCI: Use helper functions to access fields in struct msi_desc Jiang Liu
2015-07-09 8:00 ` David Miller [this message]
2015-07-09 8:00 ` [RFC Patch V1 08/12] " Jiang Liu
2015-07-12 11:18 ` Jingoo Han
2015-07-09 8:00 ` [RFC Patch V1 09/12] genirq: Move msi_list from struct pci_dev to struct device Jiang Liu
2015-07-10 0:19 ` Paul Gortmaker
2015-07-21 22:02 ` Thomas Gleixner
2015-07-09 8:00 ` [RFC Patch V1 10/12] genirq, PCI: Store 'struct device *' instead 'struct pci_dev *' in struct msi_desc Jiang Liu
2015-07-09 8:00 ` [RFC Patch V1 11/12] genirq, PCI: Reorginize struct msi_desc to prepare for support of generic MSI Jiang Liu
2015-07-10 12:41 ` Marc Zyngier
2015-07-09 8:00 ` [RFC Patch V1 12/12] genirq, PCI: Move alloc_msi_entry() from PCI MSI code into generic MSI code Jiang Liu
2015-07-10 1:41 ` [RFC Patch V1 00/12] Reorganize struct msi_desc to prepare for support of generic MSI Yijing Wang
2015-07-10 12:54 ` Marc Zyngier
2015-07-21 8:31 ` Thomas Gleixner
2015-07-21 13:30 ` Bjorn Helgaas
2015-07-21 15:51 ` Thomas Gleixner
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=20150709.010045.1327001449508270216.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=eric.snowberg@oracle.com \
--cc=grant.likely@linaro.org \
--cc=jiang.liu@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mingo@redhat.com \
--cc=sparclinux@vger.kernel.org \
--cc=stuart.yoder@freescale.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=wangyijing@huawei.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).