From: Greg KH <gregkh@linuxfoundation.org>
To: Alexandru Gagniuc <alexandru.gagniuc@hp.com>
Cc: stable@vger.kernel.org, qin.wan@hp.com, andreas.noever@gmail.com,
michael.jamet@intel.com, mika.westerberg@linux.intel.com,
YehezkelShB@gmail.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org,
Alexandru Gagniuc <mr.nuke.me@gmail.com>
Subject: Re: [PATCH 6.6 00/14] Backport thunderbolt fix(es) from v6.9
Date: Wed, 2 Oct 2024 11:56:48 +0200 [thread overview]
Message-ID: <2024100236-carload-oblong-d631@gregkh> (raw)
In-Reply-To: <20241001173109.1513-1-alexandru.gagniuc@hp.com>
On Tue, Oct 01, 2024 at 05:30:55PM +0000, Alexandru Gagniuc wrote:
> From: Alexandru Gagniuc <mr.nuke.me@gmail.com>
>
> These patches resolve thunderbolt issues on Intel Raptor Lake systems.
> With a monitor connected to a HP Thunderbolt G4 dock, the display
> sometimes stops working after resume.
>
> The kernel reports an issue with the DisplayPort MST topology, the
> full backtrace being pasted below. This failure is since v6.9-rc1 by
> commit b4734507ac55 ("thunderbolt: Improve DisplayPort tunnel setup
> process to be more robust"). The other commits are dependencies such
> that all changes apply cleanly without needing modification.
All now queued up, thanks!
greg k-h
prev parent reply other threads:[~2024-10-02 9:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 17:30 [PATCH 6.6 00/14] Backport thunderbolt fix(es) from v6.9 Alexandru Gagniuc
2024-10-01 17:30 ` [PATCH 6.6 01/14] thunderbolt: Fix debug log when DisplayPort adapter not available for pairing Alexandru Gagniuc
2024-10-01 17:30 ` [PATCH 6.6 02/14] thunderbolt: Use tb_tunnel_dbg() where possible to make logging more consistent Alexandru Gagniuc
2024-10-01 17:30 ` [PATCH 6.6 03/14] thunderbolt: Expose tb_tunnel_xxx() log macros to the rest of the driver Alexandru Gagniuc
2024-10-01 17:30 ` [PATCH 6.6 04/14] thunderbolt: Create multiple DisplayPort tunnels if there are more DP IN/OUT pairs Alexandru Gagniuc
2024-10-01 17:31 ` [PATCH 6.6 05/14] thunderbolt: Use constants for path weight and priority Alexandru Gagniuc
2024-10-01 17:31 ` [PATCH 6.6 06/14] thunderbolt: Use weight constants in tb_usb3_consumed_bandwidth() Alexandru Gagniuc
2024-10-01 17:31 ` [PATCH 6.6 07/14] thunderbolt: Make is_gen4_link() available to the rest of the driver Alexandru Gagniuc
2024-10-01 17:31 ` [PATCH 6.6 08/14] thunderbolt: Change bandwidth reservations to comply USB4 v2 Alexandru Gagniuc
2024-10-01 17:31 ` [PATCH 6.6 09/14] thunderbolt: Introduce tb_port_path_direction_downstream() Alexandru Gagniuc
2024-10-01 17:31 ` [PATCH 6.6 10/14] thunderbolt: Introduce tb_for_each_upstream_port_on_path() Alexandru Gagniuc
2024-10-01 17:31 ` [PATCH 6.6 11/14] thunderbolt: Introduce tb_switch_depth() Alexandru Gagniuc
2024-10-01 17:31 ` [PATCH 6.6 12/14] thunderbolt: Add support for asymmetric link Alexandru Gagniuc
2024-10-01 17:31 ` [PATCH 6.6 13/14] thunderbolt: Configure asymmetric link if needed and bandwidth allows Alexandru Gagniuc
2024-10-01 17:31 ` [PATCH 6.6 14/14] thunderbolt: Improve DisplayPort tunnel setup process to be more robust Alexandru Gagniuc
2024-10-02 9:56 ` Greg KH [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=2024100236-carload-oblong-d631@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=YehezkelShB@gmail.com \
--cc=alexandru.gagniuc@hp.com \
--cc=andreas.noever@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=mr.nuke.me@gmail.com \
--cc=qin.wan@hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox