From: patchwork-bot+netdevbpf@kernel.org
To: Fan XinRan <shinjiangjiang@gmail.com>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, andrew+netdev@lunn.ch,
edumazet@google.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, mika.westerberg@linux.intel.com,
davem@davemloft.net, YehezkelShB@gmail.com, westeri@kernel.org
Subject: Re: [PATCH net v2] net: thunderbolt: Tear down DMA paths before stopping the rings
Date: Thu, 06 Aug 2026 15:50:19 +0000 [thread overview]
Message-ID: <178603141989.1348318.7897759415546724643.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260803-b4-tbnet-teardown-v2-1-27de6a13ca2d@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 03 Aug 2026 14:38:50 +0000 you wrote:
> From: Fan XinRan <shinjiangjiang@gmail.com>
>
> tbnet_tear_down() stops both rings and frees their frame buffers before
> calling tb_xdomain_disable_paths(). tb_ring_stop() zeroes the ring's
> descriptor base and tbnet_free_buffers() unmaps and frees the pages the
> frames sit in, so by the time __tb_path_deactivate_hop() polls the hop's
> 'pending' bit, anything still in flight has nowhere to drain to.
>
> [...]
Here is the summary with links:
- [net,v2] net: thunderbolt: Tear down DMA paths before stopping the rings
https://git.kernel.org/netdev/net/c/68bf02b6b4ad
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-06 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 14:38 [PATCH net v2] net: thunderbolt: Tear down DMA paths before stopping the rings Fan XinRan via B4 Relay
2026-08-03 14:38 ` Fan XinRan
2026-08-06 15:50 ` 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=178603141989.1348318.7897759415546724643.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=YehezkelShB@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.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=shinjiangjiang@gmail.com \
--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.