From: Florian Fainelli <f.fainelli@gmail.com>
To: Ray Jui <rjui@broadcom.com>, Bjorn Helgaas <bhelgaas@google.com>,
Arnd Bergmann <arnd@arndb.de>, Hauke Mehrtens <hauke@hauke-m.de>,
Paul Bolle <pebolle@tiscali.nl>
Cc: Dmitry Torokhov <dtor@google.com>,
Anatol Pomazau <anatol@google.com>,
Scott Branden <sbranden@broadcom.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com,
devicetree@vger.kernel.org
Subject: Re: [PATCH v6 4/4] ARM: dts: enable PCIe support for Cygnus
Date: Fri, 13 Mar 2015 09:21:15 -0700 [thread overview]
Message-ID: <55030E7B.8080305@gmail.com> (raw)
In-Reply-To: <1426097169-20805-5-git-send-email-rjui@broadcom.com>
On 11/03/15 11:06, Ray Jui wrote:
> Add PCIe device nodes in bcm-cygnus.dtsi but keep them disabled there.
> Only enable them for bcm958300k where PCIe interfaces are populated
>
> Signed-off-by: Ray Jui <rjui@broadcom.com>
> Reviewed-by: Scott Branden <sbranden@broadcom.com>
Applied to devicetree/next with Arnd's acked-by, thanks!
--
Florian
prev parent reply other threads:[~2015-03-13 16:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 18:06 [PATCH v6 0/4] pci: iproc: Add Broadcom iProc PCIe support Ray Jui
2015-03-11 18:06 ` [PATCH v6 1/4] PCI: Export symbols of PCI functions Ray Jui
2015-03-11 18:06 ` [PATCH v6 2/4] pci: iProc: define iProc PCIe platform bus binding Ray Jui
2015-03-12 21:14 ` Bjorn Helgaas
2015-03-13 11:07 ` Arnd Bergmann
2015-03-11 18:06 ` [PATCH v6 3/4] pci: iproc: Add Broadcom iProc PCIe support Ray Jui
2015-03-12 21:08 ` Bjorn Helgaas
[not found] ` <20150312210856.GF7346-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2015-03-13 0:17 ` Ray Jui
2015-03-11 18:06 ` [PATCH v6 4/4] ARM: dts: enable PCIe support for Cygnus Ray Jui
2015-03-13 16:21 ` Florian Fainelli [this message]
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=55030E7B.8080305@gmail.com \
--to=f.fainelli@gmail.com \
--cc=anatol@google.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=dtor@google.com \
--cc=hauke@hauke-m.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=rjui@broadcom.com \
--cc=sbranden@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).