All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: kmahammadraf <kmahammadraf@marvell.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	sgoutham@marvell.com, rkannoth@marvell.com, gakula@marvell.com,
	sbhatta@marvell.com, andrew+netdev@lunn.ch, davem@davemloft.net,
	edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
	kirankumark@marvell.com
Subject: Re: [PATCH net] octeontx2-af: fix inner LC ltype match for RSS flowkey
Date: Wed, 28 Oct 2026 09:00:04 +0000	[thread overview]
Message-ID: <179317800484.591477.12027096474618287869.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261023071905.2922825-1-kmahammadraf@marvell.com>

Hello:

This patch was applied to netdev/net.git (main)
by Dave Miller <davem@davem-thinkpadp1gen8.ibmlond.csb>:

On Fri, 23 Oct 2026 07:19:05 +0000 you wrote:
> From: Kiran Kumar K <kirankumark@marvell.com>
> 
> Inner LC ltypes differ from outer LC ltypes, but RSS flowkey programming
> was using outer LC IP/IP6 ltype masks for inner IP keys.
> 
> For inner IPv4/IPv6, match only the base IP ltype and do not include
> extension-header matches. Keep existing outer LC masks unchanged.
> 
> [...]

Here is the summary with links:
  - [net] octeontx2-af: fix inner LC ltype match for RSS flowkey
    https://git.kernel.org/netdev/net/c/22dd6bb2bafd

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



      parent reply	other threads:[~2026-10-28  9:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-23  7:19 [PATCH net] octeontx2-af: fix inner LC ltype match for RSS flowkey kmahammadraf
2026-10-23  7:22 ` netdev-bot+sinfo
2026-10-27  7:56 ` netdev-bot+sashiko
2026-10-28  9: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=179317800484.591477.12027096474618287869.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=gakula@marvell.com \
    --cc=kirankumark@marvell.com \
    --cc=kmahammadraf@marvell.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rkannoth@marvell.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 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.