All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Satish Kharat <satishkh@cisco.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
	sebaddel@cisco.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/2] enic: fix V2 VF mailbox reply matching and carrier reopen
Date: Fri, 04 Sep 2026 02:20:09 +0000	[thread overview]
Message-ID: <178848840914.4121988.4620731754860691922.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260830-b4-enic-v2-mbox-fixes-net-v1-0-23adf9bfd426@cisco.com>

Hello:

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

On Sun, 30 Aug 2026 15:22:51 -0700 you wrote:
> Preserve ENIC V2 VF carrier state across netdev reopen and match mailbox
> replies to their originating requests.
> 
> A V2 VF receives carrier state from PF MBOX notifications. enic_stop()
> forces carrier off, but enic_open() does not request another notification
> or restore the previous state. An ordinary netdev close/open can therefore
> leave the VF without carrier until the PF sends another link-state
> notification.
> 
> [...]

Here is the summary with links:
  - [net,1/2] enic: preserve V2 VF carrier across netdev reopen
    https://git.kernel.org/netdev/net/c/b752e041d584
  - [net,2/2] enic: match mailbox replies to request numbers
    https://git.kernel.org/netdev/net/c/8972d252f495

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-09-04  2:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-30 22:22 [PATCH net 0/2] enic: fix V2 VF mailbox reply matching and carrier reopen Satish Kharat
2026-08-30 22:22 ` [PATCH net 1/2] enic: preserve V2 VF carrier across netdev reopen Satish Kharat
2026-08-30 22:22 ` [PATCH net 2/2] enic: match mailbox replies to request numbers Satish Kharat
2026-09-03 15:23   ` [net,2/2] " netdev-bot+sashiko
2026-09-04  2:20 ` 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=178848840914.4121988.4620731754860691922.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=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=satishkh@cisco.com \
    --cc=sebaddel@cisco.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.