Linux on Apple ARM platform development
 help / color / mirror / Atom feed
From: Sven Peter <sven@kernel.org>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Andreas Noever <andreas.noever@gmail.com>,
	Mika Westerberg <westeri@kernel.org>,
	Yehezkel Bernat <YehezkelShB@gmail.com>,
	Konrad Dybcio <konradybcio@kernel.org>,
	asahi@lists.linux.dev, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v3 0/7] thunderbolt: Fix DP tunnel teardown while an async DPRX read is running
Date: Tue, 1 Sep 2026 10:53:30 +0200	[thread overview]
Message-ID: <7f269572-7dae-4894-b148-56314cd21bbd@kernel.org> (raw)
In-Reply-To: <20260901081924.GA106095@black.igk.intel.com>

Hi,

On 9/1/26 10:19, Mika Westerberg wrote:
>> ---
>> Sven Peter (7):
>>        thunderbolt: Hold a router reference for each allocated HopID
>>        thunderbolt: Make the DP tunnel activation callback mandatory
>>        thunderbolt: Fix domain reference leak when DPRX read is canceled
>>        thunderbolt: Don't access a DP tunnel after its DPRX read was canceled
>>        thunderbolt: Mark discovered tunnels as active
>>        thunderbolt: Tear down inactive DP tunnels when the domain is stopped
> Applied 1-6 to thunderbolt.git/fixes, with minor changes in the commit
> messages and the condition in patch 6, thanks! Please check that it is
> okay. My testing at least it works as expected.

Looks good to me, thanks!

>
>>        thunderbolt: Drop the DP tunnel activation callback data
> Since this one is a cleanup, I wonder if you can send it again later when
> the DPRX fixes have landed? I typically base my next branch after -rc1 and
> don't merge fixes/rc's there constantly so preferably after v7.4-rc1 is
> released.

Sure, I can resend it after 7.4-rc1 is out.


Sven



      reply	other threads:[~2026-09-01  8:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-29  8:08 [PATCH v3 0/7] thunderbolt: Fix DP tunnel teardown while an async DPRX read is running Sven Peter
2026-08-29  8:08 ` [PATCH v3 1/7] thunderbolt: Hold a router reference for each allocated HopID Sven Peter
2026-08-29  8:08 ` [PATCH v3 2/7] thunderbolt: Make the DP tunnel activation callback mandatory Sven Peter
2026-08-29  8:08 ` [PATCH v3 3/7] thunderbolt: Fix domain reference leak when DPRX read is canceled Sven Peter
2026-08-29  8:08 ` [PATCH v3 4/7] thunderbolt: Don't access a DP tunnel after its DPRX read was canceled Sven Peter
2026-08-29  8:08 ` [PATCH v3 5/7] thunderbolt: Mark discovered tunnels as active Sven Peter
2026-08-29  8:08 ` [PATCH v3 6/7] thunderbolt: Tear down inactive DP tunnels when the domain is stopped Sven Peter
2026-08-29  8:08 ` [PATCH v3 7/7] thunderbolt: Drop the DP tunnel activation callback data Sven Peter
2026-09-01  8:19 ` [PATCH v3 0/7] thunderbolt: Fix DP tunnel teardown while an async DPRX read is running Mika Westerberg
2026-09-01  8:53   ` Sven Peter [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=7f269572-7dae-4894-b148-56314cd21bbd@kernel.org \
    --to=sven@kernel.org \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=asahi@lists.linux.dev \
    --cc=konradybcio@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox