From: Florian Fainelli <f.fainelli@gmail.com>
To: Ray Jui <rjui@broadcom.com>, Bjorn Helgaas <bhelgaas@google.com>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
Arnd Bergmann <arnd@arndb.de>, Hauke Mehrtens <hauke@hauke-m.de>,
linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com, linux-pci@vger.kernel.org
Subject: Re: [PATCH v5 5/5] ARM: dts: Enable MSI support for Broadcom Cygnus
Date: Mon, 07 Dec 2015 14:15:32 -0800 [thread overview]
Message-ID: <56660504.6040308@gmail.com> (raw)
In-Reply-To: <1449250502-10679-6-git-send-email-rjui@broadcom.com>
On 04/12/15 09:35, Ray Jui wrote:
> Enable MSI support for Broadcom Cygnus platforms
>
> Signed-off-by: Ray Jui <rjui@broadcom.com>
> Reviewed-by: Anup Patel <anup.patel@broadcom.com>
> Reviewed-by: Pramod KUMAR <pramodku@broadcom.com>
> Reviewed-by: Vikram Prakash <vikramp@broadcom.com>
> Reviewed-by: Scott Branden <sbranden@broadcom.com>
Applied to devicetree/next, thanks!
--
Florian
next prev parent reply other threads:[~2015-12-07 22:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 17:34 [PATCH v5 0/5] Add iProc PCIe PAXC and MSI support Ray Jui
2015-12-04 17:34 ` [PATCH v5 1/5] PCI: iproc: Update iProc PCIe device tree binding Ray Jui
2015-12-04 17:34 ` [PATCH v5 2/5] PCI: iproc: Add PAXC interface support Ray Jui
2015-12-04 17:35 ` [PATCH v5 3/5] PCI: iproc: Add iProc PCIe MSI device tree binding Ray Jui
2015-12-04 17:35 ` [PATCH v5 4/5] PCI: iproc: Add iProc PCIe MSI support Ray Jui
2015-12-04 18:01 ` Marc Zyngier
2015-12-04 17:35 ` [PATCH v5 5/5] ARM: dts: Enable MSI support for Broadcom Cygnus Ray Jui
2015-12-07 22:15 ` Florian Fainelli [this message]
2015-12-07 17:01 ` [PATCH v5 0/5] Add iProc PCIe PAXC and MSI support Bjorn Helgaas
2015-12-07 20:32 ` Florian Fainelli
2015-12-07 21:33 ` Bjorn Helgaas
2015-12-07 22:15 ` Florian Fainelli
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=56660504.6040308@gmail.com \
--to=f.fainelli@gmail.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=hauke@hauke-m.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=rjui@broadcom.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).