From: David Miller <davem@davemloft.net>
To: hauke@hauke-m.de
Cc: netdev@vger.kernel.org, andrew@lunn.ch,
vivien.didelot@savoirfairelinux.com, f.fainelli@gmail.com,
john@phrozen.org, linux-mips@linux-mips.org, dev@kresin.me,
hauke.mehrtens@intel.com, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 net-next 0/6] Add support for Lantiq / Intel vrx200 network
Date: Thu, 13 Sep 2018 08:15:02 -0700 (PDT) [thread overview]
Message-ID: <20180913.081502.621496165436800090.davem@davemloft.net> (raw)
In-Reply-To: <20180909201647.32727-1-hauke@hauke-m.de>
From: Hauke Mehrtens <hauke@hauke-m.de>
Date: Sun, 9 Sep 2018 22:16:41 +0200
> This adds basic support for the GSWIP (Gigabit Switch) found in the
> VRX200 SoC.
> There are different versions of this IP core used in different SoCs, but
> this driver was currently only tested on the VRX200 SoC line, for other
> SoCs this driver probably need some adoptions to work.
>
> I also plan to add Layer 2 offloading to the DSA driver and later also
> layer 3 offloading which is supported by the PPE HW block.
>
> All these patches should go through the net-next tree.
>
> This depends on the patch "MIPS: lantiq: dma: add dev pointer" which
> should go into 4.19.
Series applied to net-next, thanks.
prev parent reply other threads:[~2018-09-13 15:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-09 20:16 [PATCH v3 net-next 0/6] Add support for Lantiq / Intel vrx200 network Hauke Mehrtens
2018-09-09 20:16 ` [PATCH v3 net-next 1/6] MIPS: lantiq: Do not enable IRQs in dma open Hauke Mehrtens
2018-09-09 20:16 ` [PATCH v3 net-next 2/6] net: dsa: Add Lantiq / Intel GSWIP tag support Hauke Mehrtens
2018-09-09 20:16 ` [PATCH v3 net-next 3/6] dt-bindings: net: Add lantiq,xrx200-net DT bindings Hauke Mehrtens
2018-09-10 12:53 ` Andrew Lunn
2018-09-11 21:33 ` Hauke Mehrtens
2018-09-10 21:49 ` Rob Herring
2018-09-09 20:16 ` [PATCH v3 net-next 4/6] net: lantiq: Add Lantiq / Intel VRX200 Ethernet driver Hauke Mehrtens
2018-09-13 15:15 ` David Miller [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=20180913.081502.621496165436800090.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=dev@kresin.me \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hauke.mehrtens@intel.com \
--cc=hauke@hauke-m.de \
--cc=john@phrozen.org \
--cc=linux-mips@linux-mips.org \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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).