From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Yehezkel Bernat <YehezkelShB@gmail.com>,
Michael Jamet <michael.jamet@intel.com>,
Lukas Wunner <lukas@wunner.de>,
Andreas Noever <andreas.noever@gmail.com>,
linux-usb@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: [GIT PULL] USB4/Thunderbolt changes for v6.15 merge window
Date: Thu, 20 Mar 2025 13:49:14 +0200 [thread overview]
Message-ID: <20250320114914.GO3713119@black.fi.intel.com> (raw)
Hi Greg,
The following changes since commit 2014c95afecee3e76ca4a56956a936e23283f05b:
Linux 6.14-rc1 (2025-02-02 15:39:26 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt.git tags/thunderbolt-for-v6.15-rc1
for you to fetch changes up to ad79c278e478ca8c1a3bf8e7a0afba8f862a48a1:
thunderbolt: Do not add non-active NVM if NVM upgrade is disabled for retimer (2025-03-17 12:24:56 +0200)
----------------------------------------------------------------
thunderbolt: Changes for v6.15 merge window
This includes following USB4/Thunderbolt changes for the v6.15 merge
window:
- Move retimer scanning to happen bit later to work better with
Pluggable USB4 devices.
- No need to add non-active NVM for retimers if NVM upgrade is not
supported.
- Cleanup for tb_tunnel_alloc_usb3().
- MAINTAINERS update.
All these have been in linux-next with no reported issues.
----------------------------------------------------------------
Alan Borzeszkowski (1):
thunderbolt: Make tb_tunnel_alloc_usb3() error paths consistent with the rest
Mika Westerberg (3):
MAINTAINERS: Use my kernel.org address for USB4/Thunderbolt work
thunderbolt: Scan retimers after device router has been enumerated
thunderbolt: Do not add non-active NVM if NVM upgrade is disabled for retimer
MAINTAINERS | 4 ++--
drivers/thunderbolt/retimer.c | 8 +++++---
drivers/thunderbolt/tb.c | 16 ++++++++++++++--
drivers/thunderbolt/tunnel.c | 16 ++++++++--------
4 files changed, 29 insertions(+), 15 deletions(-)
next reply other threads:[~2025-03-20 11:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 11:49 Mika Westerberg [this message]
2025-03-20 13:41 ` [GIT PULL] USB4/Thunderbolt changes for v6.15 merge window Greg Kroah-Hartman
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=20250320114914.GO3713119@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=michael.jamet@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox