From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Andreas Noever <andreas.noever@gmail.com>,
Michael Jamet <michael.jamet@intel.com>,
Yehezkel Bernat <YehezkelShB@gmail.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Lukas Wunner <lukas@wunner.de>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] Thunderbolt fixes for v5.2-rc6
Date: Wed, 19 Jun 2019 14:08:02 +0300 [thread overview]
Message-ID: <20190619110802.GT2640@lahna.fi.intel.com> (raw)
Hi Greg,
The following changes since commit d1fdb6d8f6a4109a4263176c84b899076a5f8008:
Linux 5.2-rc4 (2019-06-08 20:24:46 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt.git tags/thunderbolt-fixes-for-v5.2-rc6
for you to fetch changes up to 0d53827d7c172f1345140f7638fe658bda1bb25d:
thunderbolt: Implement CIO reset correctly for Titan Ridge (2019-06-14 14:25:43 +0300)
----------------------------------------------------------------
thunderbolt: Fixes for v5.2-rc6
This includes two fixes for issues found during the current release
cycle:
- Fix runtime PM regression when device is authorized after the
controller is runtime suspended.
- Correct CIO reset flow for Titan Ridge.
----------------------------------------------------------------
Mika Westerberg (2):
thunderbolt: Make sure device runtime resume completes before taking domain lock
thunderbolt: Implement CIO reset correctly for Titan Ridge
drivers/thunderbolt/icm.c | 188 +++++++++++++++++++++++++++++--------------
drivers/thunderbolt/switch.c | 45 ++++++++---
drivers/thunderbolt/tb.h | 7 ++
3 files changed, 167 insertions(+), 73 deletions(-)
next reply other threads:[~2019-06-19 11:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 11:08 Mika Westerberg [this message]
2019-06-19 17:22 ` [GIT PULL] Thunderbolt fixes for v5.2-rc6 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=20190619110802.GT2640@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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).