From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Yehezkel Bernat <YehezkelShB@gmail.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.20 merge window
Date: Tue, 3 Feb 2026 07:31:40 +0100 [thread overview]
Message-ID: <20260203063140.GC2275908@black.igk.intel.com> (raw)
Hi Greg,
The following changes since commit f8f9c1f4d0c7a64600e2ca312dec824a0bc2f1da:
Linux 6.19-rc3 (2025-12-28 13:24: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.20-rc1
for you to fetch changes up to 062191adfde0b11b01656ea6db51a9385fa3d104:
thunderbolt: Log path activation failures without WARN backtraces (2026-01-05 12:14:43 +0100)
----------------------------------------------------------------
thunderbolt: Changes for v6.20 merge window
This includes following USB4/Thunderbolt changes for the v6.20 merge
window:
- Tiny documentation update
- Switch to use tb_warn() when logging path activation failures.
Both have been in linux-next with no reported issues.
----------------------------------------------------------------
Chia-Lin Kao (AceLan) (1):
thunderbolt: Log path activation failures without WARN backtraces
Jaime Saguillo Revilla (1):
docs: admin-guide: thunderbolt: Replace ifconfig with ip
Documentation/admin-guide/thunderbolt.rst | 2 +-
drivers/thunderbolt/path.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
next reply other threads:[~2026-02-03 6:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 6:31 Mika Westerberg [this message]
2026-02-05 16:05 ` [GIT PULL] USB4/Thunderbolt changes for v6.20 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=20260203063140.GC2275908@black.igk.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 \
/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