From: patchwork-bot+netdevbpf@kernel.org
To: DENG Qingfang <dqfext@gmail.com>
Cc: sean.wang@mediatek.com, Landen.Chao@mediatek.com, andrew@lunn.ch,
vivien.didelot@gmail.com, f.fainelli@gmail.com,
olteanv@gmail.com, davem@davemloft.net, kuba@kernel.org,
matthias.bgg@gmail.com, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] net: dsa: mt7530: drop untagged frames on VLAN-aware ports without PVID
Date: Fri, 06 Aug 2021 11:10:06 +0000 [thread overview]
Message-ID: <162824820631.31954.9293662469034354478.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210806034713.734853-1-dqfext@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Fri, 6 Aug 2021 11:47:11 +0800 you wrote:
> The driver currently still accepts untagged frames on VLAN-aware ports
> without PVID. Use PVC.ACC_FRM to drop untagged frames in that case.
>
> Signed-off-by: DENG Qingfang <dqfext@gmail.com>
> ---
> v1 -> v2: Avoid setting PVID to 0 on the CPU port.
>
> [...]
Here is the summary with links:
- [net-next,v2] net: dsa: mt7530: drop untagged frames on VLAN-aware ports without PVID
https://git.kernel.org/netdev/net-next/c/8fbebef80107
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: DENG Qingfang <dqfext@gmail.com>
Cc: sean.wang@mediatek.com, Landen.Chao@mediatek.com, andrew@lunn.ch,
vivien.didelot@gmail.com, f.fainelli@gmail.com,
olteanv@gmail.com, davem@davemloft.net, kuba@kernel.org,
matthias.bgg@gmail.com, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] net: dsa: mt7530: drop untagged frames on VLAN-aware ports without PVID
Date: Fri, 06 Aug 2021 11:10:06 +0000 [thread overview]
Message-ID: <162824820631.31954.9293662469034354478.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210806034713.734853-1-dqfext@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Fri, 6 Aug 2021 11:47:11 +0800 you wrote:
> The driver currently still accepts untagged frames on VLAN-aware ports
> without PVID. Use PVC.ACC_FRM to drop untagged frames in that case.
>
> Signed-off-by: DENG Qingfang <dqfext@gmail.com>
> ---
> v1 -> v2: Avoid setting PVID to 0 on the CPU port.
>
> [...]
Here is the summary with links:
- [net-next,v2] net: dsa: mt7530: drop untagged frames on VLAN-aware ports without PVID
https://git.kernel.org/netdev/net-next/c/8fbebef80107
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: DENG Qingfang <dqfext@gmail.com>
Cc: sean.wang@mediatek.com, Landen.Chao@mediatek.com, andrew@lunn.ch,
vivien.didelot@gmail.com, f.fainelli@gmail.com,
olteanv@gmail.com, davem@davemloft.net, kuba@kernel.org,
matthias.bgg@gmail.com, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] net: dsa: mt7530: drop untagged frames on VLAN-aware ports without PVID
Date: Fri, 06 Aug 2021 11:10:06 +0000 [thread overview]
Message-ID: <162824820631.31954.9293662469034354478.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210806034713.734853-1-dqfext@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Fri, 6 Aug 2021 11:47:11 +0800 you wrote:
> The driver currently still accepts untagged frames on VLAN-aware ports
> without PVID. Use PVC.ACC_FRM to drop untagged frames in that case.
>
> Signed-off-by: DENG Qingfang <dqfext@gmail.com>
> ---
> v1 -> v2: Avoid setting PVID to 0 on the CPU port.
>
> [...]
Here is the summary with links:
- [net-next,v2] net: dsa: mt7530: drop untagged frames on VLAN-aware ports without PVID
https://git.kernel.org/netdev/net-next/c/8fbebef80107
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-08-06 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 3:47 [PATCH net-next v2] net: dsa: mt7530: drop untagged frames on VLAN-aware ports without PVID DENG Qingfang
2021-08-06 3:47 ` DENG Qingfang
2021-08-06 3:47 ` DENG Qingfang
2021-08-06 11:10 ` patchwork-bot+netdevbpf [this message]
2021-08-06 11:10 ` patchwork-bot+netdevbpf
2021-08-06 11:10 ` patchwork-bot+netdevbpf
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=162824820631.31954.9293662469034354478.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Landen.Chao@mediatek.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=sean.wang@mediatek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.