From: Florian Fainelli <f.fainelli@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
linux-arm-kernel@lists.infradead.org
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>, Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Jon Mason <jonmason@broadcom.com>,
"maintainer:BROADCOM IPROC ARM ARCHITECTURE"
<bcm-kernel-feedback-list@broadcom.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
andrew@lunn.ch, rmk+kernel@armlinux.org.uk
Subject: Re: [PATCH v3 0/3] ARM: NSP updates to support switch interrupts/SFP
Date: Thu, 13 Sep 2018 11:10:20 -0700 [thread overview]
Message-ID: <5751f9e2-6056-37cc-4749-cb8509b56916@gmail.com> (raw)
In-Reply-To: <20180831192039.11842-1-f.fainelli@gmail.com>
On 08/31/18 12:20, Florian Fainelli wrote:
> Hi all,
>
> This patch series updates the ARM NSP DTS and BCM958625HR in order to
> support the SFP connected to port 5 on these reference boards.
>
> I will be submitting the functional changes to drivers/net/dsa/b53 once
> net-next opens back up, but this is largely independent from getting
> these 3 patches out.
Series applied to devicetree/next.
--
Florian
prev parent reply other threads:[~2018-09-13 18:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 19:20 [PATCH v3 0/3] ARM: NSP updates to support switch interrupts/SFP Florian Fainelli
2018-08-31 19:20 ` [PATCH v3 1/3] ARM: dts: NSP: Enable SFP on bcm958625hr Florian Fainelli
2018-09-04 20:39 ` Ray Jui
2018-08-31 19:20 ` [PATCH v3 2/3] dt-bindings: net: dsa: Document B53 SRAB interrupts and registers Florian Fainelli
2018-09-10 19:57 ` Rob Herring
2018-08-31 19:20 ` [PATCH v3 3/3] ARM: dts: NSP: Wire up switch interrupts Florian Fainelli
2018-09-13 18:10 ` 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=5751f9e2-6056-37cc-4749-cb8509b56916@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=jonmason@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rjui@broadcom.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=robh+dt@kernel.org \
--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).