From: Florian Fainelli <f.fainelli@gmail.com>
To: patchwork-bot+netdevbpf@kernel.org,
Eldar Gasanov <eldargasanov2@gmail.com>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, vivien.didelot@gmail.com,
olteanv@gmail.com, davem@davemloft.net, kuba@kernel.org
Subject: Re: [PATCH] mv88e6xxx: fixed adding vlan 0
Date: Mon, 21 Jun 2021 14:52:36 -0700 [thread overview]
Message-ID: <7beb3632-fa36-4d12-ed20-65400dd4e0df@gmail.com> (raw)
In-Reply-To: <162431220437.17422.6366269633750145571.git-patchwork-notify@kernel.org>
On 6/21/21 2:50 PM, patchwork-bot+netdevbpf@kernel.org wrote:
> Hello:
>
> This patch was applied to netdev/net.git (refs/heads/master):
>
> On Mon, 21 Jun 2021 11:54:38 +0300 you wrote:
>> 8021q module adds vlan 0 to all interfaces when it starts.
>> When 8021q module is loaded it isn't possible to create bond
>> with mv88e6xxx interfaces, bonding module dipslay error
>> "Couldn't add bond vlan ids", because it tries to add vlan 0
>> to slave interfaces.
>>
>> There is unexpected behavior in the switch. When a PVID
>> is assigned to a port the switch changes VID to PVID
>> in ingress frames with VID 0 on the port. Expected
>> that the switch doesn't assign PVID to tagged frames
>> with VID 0. But there isn't a way to change this behavior
>> in the switch.
>>
>> [...]
>
> Here is the summary with links:
> - mv88e6xxx: fixed adding vlan 0
> https://git.kernel.org/netdev/net/c/b8b79c414eca
This version would ideally have been applied instead:
https://lore.kernel.org/netdev/20210621134703.33933-1-eldargasanov2@gmail.com/
--
Florian
next prev parent reply other threads:[~2021-06-21 21:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 8:54 [PATCH] mv88e6xxx: fixed adding vlan 0 Eldar Gasanov
2021-06-21 10:04 ` Vladimir Oltean
2021-06-21 11:30 ` Marek Behún
2021-06-21 21:50 ` patchwork-bot+netdevbpf
2021-06-21 21:52 ` Florian Fainelli [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-21 8:41 Eldar Gasanov
2021-05-17 6:25 Eldar Gasanov
2021-05-17 15:00 ` Vladimir Oltean
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=7beb3632-fa36-4d12-ed20-65400dd4e0df@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=eldargasanov2@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=patchwork-bot+netdevbpf@kernel.org \
--cc=vivien.didelot@gmail.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).