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 fixes for v6.12-rc5
Date: Fri, 25 Oct 2024 09:15:42 +0300 [thread overview]
Message-ID: <20241025061542.GL275077@black.fi.intel.com> (raw)
Hi Greg,
The following changes since commit 8cf0b93919e13d1e8d4466eb4080a4c4d9d66d7b:
Linux 6.12-rc2 (2024-10-06 15:32:27 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt.git tags/thunderbolt-for-v6.12-rc5
for you to fetch changes up to 3cea8af2d1a9ae5869b47c3dabe3b20f331f3bbd:
thunderbolt: Honor TMU requirements in the domain when setting TMU mode (2024-10-21 09:42:42 +0300)
----------------------------------------------------------------
thunderbolt: Fixes for v6.12-rc5
This includes following USB4/Thunderbolt fixes for v6.12-rc5:
- Fix KASAN reported stack out-of-bounds read
- Honor Time Management Unit (TMU) requirements in the domain when
configuring TMU mode of a newly plugged router.
Both have been in linux-next with no reported issues.
----------------------------------------------------------------
Gil Fine (1):
thunderbolt: Honor TMU requirements in the domain when setting TMU mode
Mika Westerberg (1):
thunderbolt: Fix KASAN reported stack out-of-bounds read in tb_retimer_scan()
drivers/thunderbolt/retimer.c | 5 +++--
drivers/thunderbolt/tb.c | 48 +++++++++++++++++++++++++++++++++++++------
2 files changed, 45 insertions(+), 8 deletions(-)
next reply other threads:[~2024-10-25 6:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 6:15 Mika Westerberg [this message]
2024-10-29 3:12 ` [GIT PULL] USB4/Thunderbolt fixes for v6.12-rc5 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=20241025061542.GL275077@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;
as well as URLs for NNTP newsgroup(s).