From: patchwork-bot+netdevbpf@kernel.org
To: Pedro Tammela <pctammela@mojatatu.com>
Cc: netdev@vger.kernel.org, jhs@mojatatu.com, stephen@networkplumber.org
Subject: Re: [PATCH iproute2 v2 0/3] tc: parse index argument correctly
Date: Sun, 05 Mar 2023 17:00:17 +0000 [thread overview]
Message-ID: <167803561759.1759.10330960403184292446.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230227184510.277561-1-pctammela@mojatatu.com>
Hello:
This series was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@networkplumber.org>:
On Mon, 27 Feb 2023 15:45:07 -0300 you wrote:
> Following the kernel side series, we fix the iproute2 side to parse the
> index argument correctly.
> It's valid in the TC architecture to pass to create a filter that
> references an action object:
> "tc filter ... action csum index 1"
>
> v1->v2:
> - Don't use matches()
>
> [...]
Here is the summary with links:
- [iproute2,v2,1/3] tc: m_csum: parse index argument correctly
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=89d7346aa908
- [iproute2,v2,2/3] tc: m_mpls: parse index argument correctly
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=af6fd6b84554
- [iproute2,v2,3/3] tc: m_nat: parse index argument correctly
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=7375ab684228
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:[~2023-03-05 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 18:45 [PATCH iproute2 v2 0/3] tc: parse index argument correctly Pedro Tammela
2023-02-27 18:45 ` [PATCH iproute2 v2 1/3] tc: m_csum: " Pedro Tammela
2023-02-27 18:45 ` [PATCH iproute2 v2 2/3] tc: m_mpls: " Pedro Tammela
2023-02-27 18:45 ` [PATCH iproute2 v2 3/3] tc: m_nat: " Pedro Tammela
2023-03-05 16:47 ` Stephen Hemminger
2023-03-05 17: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=167803561759.1759.10330960403184292446.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=pctammela@mojatatu.com \
--cc=stephen@networkplumber.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 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.