From: patchwork-bot+netdevbpf@kernel.org
To: Boris Sukholitko <boris.sukholitko@broadcom.com>
Cc: netdev@vger.kernel.org, jhs@mojatatu.com, jiri@resnulli.us,
xiyou.wangcong@gmail.com, davem@davemloft.net,
linux-kselftest@vger.kernel.org, shuah@kernel.org,
ilya.lifshits@broadcom.com, shmulik.ladkani@gmail.com,
kuba@kernel.org, dcaratti@redhat.com
Subject: Re: [PATCH net-next v4 0/3] net/sched: act_vlan: Fix modify to allow 0
Date: Wed, 02 Jun 2021 00:00:04 +0000 [thread overview]
Message-ID: <162259200425.18494.7708189927860051377.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210601123052.3887-1-boris.sukholitko@broadcom.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Tue, 1 Jun 2021 15:30:49 +0300 you wrote:
> Currently vlan modification action checks existence of vlan priority by
> comparing it to 0. Therefore it is impossible to modify existing vlan
> tag to have priority 0.
>
> For example, the following tc command will change the vlan id but will
> not affect vlan priority:
>
> [...]
Here is the summary with links:
- [net-next,v4,1/3] net/sched: act_vlan: Fix modify to allow 0
https://git.kernel.org/netdev/net-next/c/9c5eee0afca0
- [net-next,v4,2/3] net/sched: act_vlan: No dump for unset priority
https://git.kernel.org/netdev/net-next/c/8323b20f1d76
- [net-next,v4,3/3] net/sched: act_vlan: Test priority 0 modification
https://git.kernel.org/netdev/net-next/c/8fd52b1f923c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-06-02 0:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 12:30 [PATCH net-next v4 0/3] net/sched: act_vlan: Fix modify to allow 0 Boris Sukholitko
2021-06-01 12:30 ` [PATCH net-next v4 1/3] " Boris Sukholitko
2021-06-01 12:30 ` [PATCH net-next v4 2/3] net/sched: act_vlan: No dump for unset priority Boris Sukholitko
2021-06-01 12:30 ` [PATCH net-next v4 3/3] net/sched: act_vlan: Test priority 0 modification Boris Sukholitko
2021-06-01 12:49 ` [PATCH net-next v4 0/3] net/sched: act_vlan: Fix modify to allow 0 Davide Caratti
2021-06-02 0:00 ` patchwork-bot+netdevbpf [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=162259200425.18494.7708189927860051377.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=boris.sukholitko@broadcom.com \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=ilya.lifshits@broadcom.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shmulik.ladkani@gmail.com \
--cc=shuah@kernel.org \
--cc=xiyou.wangcong@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).