From: patchwork-bot+netdevbpf@kernel.org
To: Fan Ye <fy15309206903@gmail.com>
Cc: westeri@kernel.org, YehezkelShB@gmail.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, andriy.shevchenko@linux.intel.com,
mika.westerberg@linux.intel.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net v3 0/2] net: thunderbolt: two fixes for the failed bring-up path
Date: Mon, 17 Aug 2026 19:45:30 +0000 [thread overview]
Message-ID: <178699593008.1691257.14492670475821229800.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260811-b4-tbnet-hopid-v3-0-9e75d1b51331@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 11 Aug 2026 13:20:48 +0000 you wrote:
> Two separate defects reached through the same branch in
> tbnet_connected_work(), found on an ASMedia ASM4242 host-to-host link
> when the peer drops out while a connection is being brought up.
>
> 1 releases the HopID the allocator handed out when it is not the one
> that was asked for. Today it stays allocated for the rest of the
> XDomain connection.
>
> [...]
Here is the summary with links:
- [net,v3,1/2] net: thunderbolt: Release the Rx HopID that was handed out on mismatch
https://git.kernel.org/netdev/net/c/2f1463554d05
- [net,v3,2/2] net: thunderbolt: Mark the connection down when bringing it up fails
(no matching commit)
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:[~2026-08-17 19:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 13:20 [PATCH net v3 0/2] net: thunderbolt: two fixes for the failed bring-up path Fan Ye via B4 Relay
2026-08-11 13:20 ` Fan Ye
2026-08-11 13:20 ` [PATCH net v3 1/2] net: thunderbolt: Release the Rx HopID that was handed out on mismatch Fan Ye via B4 Relay
2026-08-11 13:20 ` Fan Ye
2026-08-11 13:20 ` [PATCH net v3 2/2] net: thunderbolt: Mark the connection down when bringing it up fails Fan Ye via B4 Relay
2026-08-11 13:20 ` Fan Ye
2026-08-13 13:10 ` [PATCH net v3 0/2] net: thunderbolt: two fixes for the failed bring-up path Simon Horman
2026-08-17 19:45 ` 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=178699593008.1691257.14492670475821229800.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=YehezkelShB@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=andriy.shevchenko@linux.intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fy15309206903@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=westeri@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.