From: andrew@lunn•ch (Andrew Lunn)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/6] staging: Introduce DPAA2 Ethernet Switch driver
Date: Tue, 19 Sep 2017 14:27:16 +0200 [thread overview]
Message-ID: <20170919122716.GC4569@lunn.ch> (raw)
In-Reply-To: <1505811698-7338-1-git-send-email-razvan.stefanescu@nxp.com>
On Tue, Sep 19, 2017 at 12:01:32PM +0300, Razvan Stefanescu wrote:
> This patchset introduces the Ethernet Switch Driver for Freescale/NXP SoCs
> with DPAA2 (DataPath Acceleration Architecture v2). The driver manages
> switch objects discovered on the fsl-mc bus. A description of the driver
> can be found in the associated README file.
Hi Razvan
You should probably Cc: netdev with these patches, if you want people
who have written switch drivers to review you code. You can also drop
linux-arm-kernel, since there is nothing ARM specific in these
patches.
Andrew
prev parent reply other threads:[~2017-09-19 12:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 9:01 [PATCH 0/6] staging: Introduce DPAA2 Ethernet Switch driver Razvan Stefanescu
2017-09-19 9:01 ` [PATCH 1/6] staging: fsl-dpaa2/ethsw: Add APIs for DPSW object Razvan Stefanescu
2017-09-19 9:01 ` [PATCH 2/6] staging: fsl-dpaa2/ethsw: Add Freescale DPAA2 Ethernet Switch driver Razvan Stefanescu
2017-09-19 9:01 ` [PATCH 3/6] staging: fsl-dpaa2/ethsw: Add ethtool support Razvan Stefanescu
2017-09-19 9:01 ` [PATCH 4/6] staging: fsl-dpaa2/ethsw: Add maintainer for Ethernet Switch driver Razvan Stefanescu
2017-09-19 9:01 ` [PATCH 5/6] staging: fsl-dpaa2/ethsw: Add README Razvan Stefanescu
2017-09-19 12:17 ` Andrew Lunn
[not found] ` <AM5PR0402MB26917E7523D582ABB0A3D0D2EC720@AM5PR0402MB2691.eurprd04.prod.outlook.com>
2017-10-03 10:07 ` Razvan Stefanescu
2017-10-03 12:38 ` Andrew Lunn
2017-09-19 9:01 ` [PATCH 6/6] staging: fsl-dpaa2/ethsw: Add TODO Razvan Stefanescu
2017-09-19 12:27 ` Andrew Lunn [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=20170919122716.GC4569@lunn.ch \
--to=andrew@lunn$(echo .)ch \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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