From: patchwork-bot+netdevbpf@kernel.org
To: Subbaraya Sundeep <sbhatta@marvell.com>
Cc: davem@davemloft.net, kuba@kernel.org, sgoutham@marvell.com,
netdev@vger.kernel.org
Subject: Re: [net PATCH 0/2] Octeontx2 minor tc fixes
Date: Tue, 26 Jul 2022 11:10:13 +0000 [thread overview]
Message-ID: <165883381395.14481.6765732902430628783.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1658650874-16459-1-git-send-email-sbhatta@marvell.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Sun, 24 Jul 2022 13:51:12 +0530 you wrote:
> This patch set fixes two problems found in tc code
> wrt to ratelimiting and when installing UDP/TCP filters.
>
> Patch 1: CN10K has different register format compared to
> CN9xx hence fixes that.
> Patch 2: Check flow mask also before installing a src/dst
> port filter, otherwise installing for one port installs for other one too.
>
> [...]
Here is the summary with links:
- [net,1/2] octeontx2-pf: cn10k: Fix egress ratelimit configuration
https://git.kernel.org/netdev/net-next/c/5ec9c514d4a0
- [net,2/2] octeontx2-pf: Fix UDP/TCP src and dst port tc filters
https://git.kernel.org/netdev/net-next/c/d351c90ce248
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:[~2022-07-26 11:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 8:21 [net PATCH 0/2] Octeontx2 minor tc fixes Subbaraya Sundeep
2022-07-24 8:21 ` [net PATCH 1/2] octeontx2-pf: cn10k: Fix egress ratelimit configuration Subbaraya Sundeep
2022-07-26 13:04 ` Paolo Abeni
2022-07-24 8:21 ` [net PATCH 2/2] octeontx2-pf: Fix UDP/TCP src and dst port tc filters Subbaraya Sundeep
2022-07-26 11:10 ` 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=165883381395.14481.6765732902430628783.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.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).