From: "Marek Behún" <kabel@kernel.org>
To: Eldar Gasanov <eldargasanov2@gmail.com>
Cc: netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH] mv88e6xxx: fixed adding vlan 0
Date: Mon, 21 Jun 2021 13:30:48 +0200 [thread overview]
Message-ID: <20210621133026.475c3564@dellmb> (raw)
In-Reply-To: <20210621085437.25777-1-eldargasanov2@gmail.com>
On Mon, 21 Jun 2021 11:54:38 +0300
Eldar Gasanov <eldargasanov2@gmail.com> 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.
>
> Signed-off-by: Eldar Gasanov <eldargasanov2@gmail.com>
Patch subject should be
net: dsa: mv88e6xxx: Fix adding VLAN 0
We use present simple tense in commit messages.
next prev parent reply other threads:[~2021-06-21 11:30 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 [this message]
2021-06-21 21:50 ` patchwork-bot+netdevbpf
2021-06-21 21:52 ` Florian Fainelli
-- 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=20210621133026.475c3564@dellmb \
--to=kabel@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=eldargasanov2@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--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).