From: David Miller <davem@davemloft.net>
To: privat@egil-hjelmeland.no
Cc: andrew@lunn.ch, vivien.didelot@savoirfairelinux.com,
f.fainelli@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net-next 0/2] net: dsa: lan9303: Learn addresses on CPU port when bridged
Date: Fri, 27 Oct 2017 23:31:16 +0900 (KST) [thread overview]
Message-ID: <20171027.233116.1305727273603339304.davem@davemloft.net> (raw)
In-Reply-To: <20171026090049.1647-1-privat@egil-hjelmeland.no>
From: Egil Hjelmeland <privat@egil-hjelmeland.no>
Date: Thu, 26 Oct 2017 11:00:47 +0200
> When CPU transmit directly to port using tag, the LAN9303 does not
> learn MAC addresses received on the CPU port into the ALR table.
> ALR learning is performed only when transmitting using ALR lookup.
>
> Solution:
> If the two external ports are bridged and the packet is not STP BPDU,
> then use ALR lookup to allow ALR learning on CPU port.
> Otherwise transmit directly to port with STP state override.
>
> The first patch moves struct lan9303 to include/linux/dsa/lan9303.h in
> order to prepare for the second patch.
>
> Changes v1 -> v2:
> - new file: include/linux/dsa/lan9303.h instead of include/linux/lan9303.h
> - include linux/if_ether.h in include/linux/dsa/lan9303.h
> - renamed lan9303_tx_use_arl to lan9303_xmit_use_arl for consistency.
> - removed inline keyword to lan9303_xmit_use_arl
Series applied, thank you!
prev parent reply other threads:[~2017-10-27 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 9:00 Egil Hjelmeland
2017-10-26 9:00 ` [PATCH v2 net-next 1/2] net: dsa: lan9303: Move struct lan9303 to include/linux/dsa/lan9303.h Egil Hjelmeland
2017-10-26 9:00 ` [PATCH v2 net-next 2/2] net: dsa: lan9303: Learn addresses on CPU port when bridged Egil Hjelmeland
2017-10-26 14:38 ` Andrew Lunn
2017-10-27 14:31 ` 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=20171027.233116.1305727273603339304.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=privat@egil-hjelmeland.no \
--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
all inboxes | Powered by JetHome®