From: Egil Hjelmeland <privat@egil-hjelmeland.no>
To: David Miller <davem@davemloft.net>
Cc: andrew@lunn.ch, vivien.didelot@savoirfairelinux.com,
f.fainelli@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] net: dsa: lan9303: Fix STP and flooding issues
Date: Thu, 2 Nov 2017 10:06:49 +0100 [thread overview]
Message-ID: <45082a4a-9233-2b00-009c-0a7e6568d61d@egil-hjelmeland.no> (raw)
In-Reply-To: <20171101.213038.799755298352005372.davem@davemloft.net>
On 01. nov. 2017 13:30, David Miller wrote:
> From: Egil Hjelmeland <privat@egil-hjelmeland.no>
> Date: Tue, 31 Oct 2017 15:47:59 +0100
>
>> This patch set finishes the STP support, and fixes flooding issues.
>>
>
> Series applied, thank you.
>
Thanks! Based on happy testing on my desktop, I conclude that the
net-next lan9303 driver has now reached a level where my employer
Zenitel can use it out of the box. We have covered everything we need
from our proprietary driver.
Our old proprietary driver can not separate the interfaces. Being able
to do so may be interesting in some custom usages of our product. And we
are very much looking forward to Andrew progressing his series for IGMP
snooping for local traffic!
Egil
prev parent reply other threads:[~2017-11-02 9:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 14:47 [PATCH net-next 0/3] net: dsa: lan9303: Fix STP and flooding issues Egil Hjelmeland
2017-10-31 14:48 ` [PATCH net-next 1/3] net: dsa: lan9303: Transmit using ALR when unicast Egil Hjelmeland
2017-11-01 12:04 ` Andrew Lunn
2017-10-31 14:48 ` [PATCH net-next 2/3] net: dsa: lan9303: Add STP ALR entry on port 0 Egil Hjelmeland
2017-11-01 12:04 ` Andrew Lunn
2017-10-31 14:48 ` [PATCH net-next 3/3] net: dsa: lan9303: lan9303_rcv set skb->offload_fwd_mark Egil Hjelmeland
2017-11-01 12:03 ` Andrew Lunn
2017-11-01 12:30 ` [PATCH net-next 0/3] net: dsa: lan9303: Fix STP and flooding issues David Miller
2017-11-02 9:06 ` Egil Hjelmeland [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=45082a4a-9233-2b00-009c-0a7e6568d61d@egil-hjelmeland.no \
--to=privat@egil-hjelmeland.no \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.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).