The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Nitin Shetty J <nshettyj@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	sgoutham@marvell.com, lcherian@marvell.com, gakula@marvell.com,
	hkelam@marvell.com, sbhatta@marvell.com, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, naveenm@marvell.com, rkannoth@marvell.com,
	kirankumark@marvell.com
Subject: Re: [PATCH net v3 0/1] octeontx2-af: Bug fixes for VF RX mode
Date: Thu, 09 Jul 2026 10:10:06 +0000	[thread overview]
Message-ID: <178359180614.3386943.3763503743823915105.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260702045616.3002773-1-nshettyj@marvell.com>

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Thu, 2 Jul 2026 10:26:15 +0530 you wrote:
> From: Kiran Kumar K <kirankumark@marvell.com>
> 
> Hello,
> 
> The patch resolves an issue where a VF changing its interface
> state could inadvertently delete the RX promiscuous and all-multicast
> MCAM rules belonging to the host PF.
> 
> [...]

Here is the summary with links:
  - [net,v3,1/1] octeontx2-af: fix VF bringup affecting PF promiscuous state
    https://git.kernel.org/netdev/net/c/fabb881df322

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-07-09 10:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02  4:56 [PATCH net v3 0/1] octeontx2-af: Bug fixes for VF RX mode nshettyj
2026-07-02  4:56 ` [PATCH net v3 1/1] octeontx2-af: fix VF bringup affecting PF promiscuous state nshettyj
2026-07-09 10: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=178359180614.3386943.3763503743823915105.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gakula@marvell.com \
    --cc=hkelam@marvell.com \
    --cc=kirankumark@marvell.com \
    --cc=kuba@kernel.org \
    --cc=lcherian@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=naveenm@marvell.com \
    --cc=netdev@vger.kernel.org \
    --cc=nshettyj@marvell.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox