All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Mengyuan Lou <mengyuanlou@net-swift.com>
Cc: netdev@vger.kernel.org, jiawenwu@trustnetic.com,
	duanqiangwen@net-swift.com, linglingzhang@net-swift.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, hramamurthy@google.com,
	jacob.e.keller@intel.com, przemyslaw.kitszel@intel.com,
	stable@vger.kernel.org
Subject: Re: [PATCH net v8] net: libwx: fix VF PM suspend/resume flow
Date: Thu, 12 Nov 2026 17:10:07 +0000	[thread overview]
Message-ID: <179450340777.540799.8922827918825455447.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261109101442.84605-1-mengyuanlou@net-swift.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon,  9 Nov 2026 18:14:42 +0800 you wrote:
> The shared PM callbacks used by txgbevf and ngbevf free queue vectors and
> disable PCI without first stopping a running VF or draining service
> activity. Resume does not re-enable PCI or restore the queues and IRQs of
> a running VF. Service work can therefore access torn-down resources, and a
> running interface is not restored correctly after resume.
> 
> Stop a running VF under RTNL before freeing its interrupt resources,
> preserving its administrative running state. Drain the service timer and
> work before disabling PCI.
> 
> [...]

Here is the summary with links:
  - [net,v8] net: libwx: fix VF PM suspend/resume flow
    https://git.kernel.org/netdev/net-next/c/a6c3e4c1f703

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-11-12 17:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09 10:14 [PATCH net v8] net: libwx: fix VF PM suspend/resume flow Mengyuan Lou
2026-11-09 10:21 ` netdev-bot+sinfo
2026-11-12 16:55   ` Jakub Kicinski
2026-11-12 13:17 ` netdev-bot+sashiko
2026-11-12 17: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=179450340777.540799.8922827918825455447.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=duanqiangwen@net-swift.com \
    --cc=edumazet@google.com \
    --cc=hramamurthy@google.com \
    --cc=jacob.e.keller@intel.com \
    --cc=jiawenwu@trustnetic.com \
    --cc=kuba@kernel.org \
    --cc=linglingzhang@net-swift.com \
    --cc=mengyuanlou@net-swift.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=stable@vger.kernel.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.