netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: john@phrozen.org
Cc: andrew@lunn.ch, f.fainelli@gmail.com,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	qsdk-review@qca.qualcomm.com
Subject: Re: [PATCH V3 0/3] net-next: dsa: add QCA8K support
Date: Fri, 16 Sep 2016 04:32:17 -0400 (EDT)	[thread overview]
Message-ID: <20160916.043217.519059245886845420.davem@davemloft.net> (raw)
In-Reply-To: <1473949601-20674-1-git-send-email-john@phrozen.org>

From: John Crispin <john@phrozen.org>
Date: Thu, 15 Sep 2016 16:26:38 +0200

> This series is based on the AR8xxx series posted by Matthieu Olivari in may
> 2015. The following changes were made since then
> 
> * fixed the nitpicks from the previous review
> * updated to latest API
> * turned it into an mdio device
> * added callbacks for fdb, bridge offloading, stp, eee, port status
> * fixed several minor issues to the port setup and arp learning
> * changed the namespacing as this driver to qca8k
> 
> The driver has so far only been tested on qca8337/N. It should work on other QCA
> switches such as the qca8327 with minor changes.

Series applied.

      parent reply	other threads:[~2016-09-16  8:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-15 14:26 [PATCH V3 0/3] net-next: dsa: add QCA8K support John Crispin
     [not found] ` <1473949601-20674-1-git-send-email-john-Pj+rj9U5foFAfugRpC6u6w@public.gmane.org>
2016-09-15 14:26   ` [PATCH V3 1/3] Documentation: devicetree: add qca8k binding John Crispin
2016-09-15 14:54     ` Andrew Lunn
     [not found]     ` <1473949601-20674-2-git-send-email-john-Pj+rj9U5foFAfugRpC6u6w@public.gmane.org>
2016-09-16  1:00       ` Florian Fainelli
2016-09-23 15:23       ` Rob Herring
2016-09-15 14:26 ` [PATCH V3 2/3] net-next: dsa: add Qualcomm tag RX/TX handler John Crispin
2016-09-15 14:26 ` [PATCH V3 3/3] net-next: dsa: add new driver for qca8xxx family John Crispin
2016-09-16  8:32 ` 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=20160916.043217.519059245886845420.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=andrew@lunn.ch \
    --cc=f.fainelli@gmail.com \
    --cc=john@phrozen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=qsdk-review@qca.qualcomm.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).