All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Roi Dayan <roid@nvidia.com>
Cc: netdev@vger.kernel.org, simon.horman@netronome.com,
	dsahern@gmail.com, zahari.doychev@linux.com,
	jianbol@mellanox.com, jhs@mojatatu.com
Subject: Re: [PATCH iproute2-next 1/1] tc flower: fix parsing vlan_id and vlan_prio
Date: Wed, 25 Nov 2020 04:50:05 +0000	[thread overview]
Message-ID: <160627980560.12972.1583906545378858314.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201124122810.46790-1-roid@nvidia.com>

Hello:

This patch was applied to iproute2/iproute2-next.git (refs/heads/main):

On Tue, 24 Nov 2020 14:28:10 +0200 you wrote:
> When protocol is vlan then eth_type is set to the vlan eth type.
> So when parsing vlan_id and vlan_prio need to check tc_proto
> is vlan and not eth_type.
> 
> Fixes: 4c551369e083 ("tc flower: use right ethertype in icmp/arp parsing")
> Signed-off-by: Roi Dayan <roid@nvidia.com>
> 
> [...]

Here is the summary with links:
  - [iproute2-next,1/1] tc flower: fix parsing vlan_id and vlan_prio
    https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=ed40b7e2ae4d

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2020-11-25  4:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-24 12:28 [PATCH iproute2-next 1/1] tc flower: fix parsing vlan_id and vlan_prio Roi Dayan
2020-11-24 12:42 ` Zahari Doychev
2020-11-25  4:46 ` David Ahern
2020-11-25  4:50 ` 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=160627980560.12972.1583906545378858314.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=dsahern@gmail.com \
    --cc=jhs@mojatatu.com \
    --cc=jianbol@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=roid@nvidia.com \
    --cc=simon.horman@netronome.com \
    --cc=zahari.doychev@linux.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.