From: patchwork-bot+netdevbpf@kernel.org
To: Guillaume Nault <gnault@redhat.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] selftests: tc: Test tc-flower's MPLS features
Date: Sat, 13 Feb 2021 01:20:09 +0000 [thread overview]
Message-ID: <161317920979.20729.55688764658160555.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1613155785.git.gnault@redhat.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Fri, 12 Feb 2021 20:05:33 +0100 you wrote:
> A couple of patches for exercising the MPLS filters of tc-flower.
>
> Patch 1 tests basic MPLS matching features: those that only work on the
> first label stack entry (that is, the mpls_label, mpls_tc, mpls_bos and
> mpls_ttl options).
>
> Patch 2 tests the more generic "mpls" and "lse" options, which allow
> matching MPLS fields beyond the first stack entry.
>
> [...]
Here is the summary with links:
- [net-next,1/2] selftests: tc: Add basic mpls_* matching support for tc-flower
https://git.kernel.org/netdev/net-next/c/203ee5cd7235
- [net-next,2/2] selftests: tc: Add generic mpls matching support for tc-flower
https://git.kernel.org/netdev/net-next/c/c09bfd9a5df9
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-02-13 1:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 19:05 [PATCH net-next 0/2] selftests: tc: Test tc-flower's MPLS features Guillaume Nault
2021-02-12 19:05 ` [PATCH net-next 1/2] selftests: tc: Add basic mpls_* matching support for tc-flower Guillaume Nault
2021-02-12 19:05 ` [PATCH net-next 2/2] selftests: tc: Add generic mpls " Guillaume Nault
2021-02-13 1:20 ` 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=161317920979.20729.55688764658160555.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=gnault@redhat.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/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).