From: patchwork-bot+netdevbpf@kernel.org
To: Subbaraya Sundeep Bhatta <sbhatta@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, sgoutham@marvell.com, lcherian@marvell.com,
gakula@marvell.com, hkelam@marvell.com, naveenm@marvell.com,
horms@kernel.org
Subject: Re: [PATCH net] octeontx2-af: Remove the PF_FUNC validation for NPC transmit rules
Date: Wed, 14 Feb 2024 09:40:27 +0000 [thread overview]
Message-ID: <170790362705.30474.13042133604652078072.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1707678038-13062-1-git-send-email-sbhatta@marvell.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Mon, 12 Feb 2024 00:30:38 +0530 you wrote:
> NPC transmit side mcam rules can use the pcifunc (in packet metadata
> added by hardware) of transmitting device for mcam lookup similar to
> the channel of receiving device at receive side.
> The commit 18603683d766 ("octeontx2-af: Remove channel verification
> while installing MCAM rules") removed the receive side channel
> verification to save hardware MCAM filters while switching packets
> across interfaces but missed removing transmit side checks.
> This patch removes transmit side rules validation.
>
> [...]
Here is the summary with links:
- [net] octeontx2-af: Remove the PF_FUNC validation for NPC transmit rules
https://git.kernel.org/netdev/net/c/858b31133dbe
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:[~2024-02-14 9:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 19:00 [PATCH net] octeontx2-af: Remove the PF_FUNC validation for NPC transmit rules Subbaraya Sundeep
2024-02-14 9:40 ` 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=170790362705.30474.13042133604652078072.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naveenm@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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