From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Konrad J Hambrick <kjhambrick@gmail.com>
Cc: linux-usb@vger.kernel.org,
"Yehezkel Bernat" <YehezkelShB@gmail.com>,
"Michael Jamet" <michael.jamet@intel.com>,
"Lukas Wunner" <lukas@wunner.de>,
"Andreas Noever" <andreas.noever@gmail.com>,
"Werner Sembach" <wse@tuxedocomputers.com>,
"Calvin Walton" <calvin.walton@kepstin.ca>,
"Marek Šanta" <teslan223@gmail.com>,
"David Binderman" <dcb314@hotmail.com>,
"Alex Balcanquall" <alex@alexbal.com>
Subject: Re: [PATCH 0/5] thunderbolt: Couple of fixes and improvements
Date: Fri, 15 Sep 2023 14:12:25 +0300 [thread overview]
Message-ID: <20230915111225.GQ1599918@black.fi.intel.com> (raw)
In-Reply-To: <CANBHt+PT9S59C-4S4riUm03fs2RKGwfVKM6i20=YUN5_-FSnWg@mail.gmail.com>
Hi,
On Fri, Sep 15, 2023 at 06:00:39AM -0500, Konrad J Hambrick wrote:
> Is there something you would like to have tested in this set of patches ?
No need, you already provided all the necessary information on the
bugzilla! Thanks a lot for testing! :)
prev parent reply other threads:[~2023-09-15 11:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 10:04 [PATCH 0/5] thunderbolt: Couple of fixes and improvements Mika Westerberg
2023-09-11 10:04 ` [PATCH 1/5] thunderbolt: Workaround an IOMMU fault on certain systems with Intel Maple Ridge Mika Westerberg
2023-09-11 10:04 ` [PATCH 2/5] thunderbolt: Check that lane 1 is in CL0 before enabling lane bonding Mika Westerberg
2023-09-11 10:04 ` [PATCH 3/5] thunderbolt: Correct TMU mode initialization from hardware Mika Westerberg
2023-09-11 10:04 ` [PATCH 4/5] thunderbolt: Apply USB 3.x bandwidth quirk only in software connection manager Mika Westerberg
2023-09-11 10:04 ` [PATCH 5/5] thunderbolt: Restart XDomain discovery handshake after failure Mika Westerberg
2023-09-15 10:10 ` [PATCH 0/5] thunderbolt: Couple of fixes and improvements Mika Westerberg
[not found] ` <CANBHt+PT9S59C-4S4riUm03fs2RKGwfVKM6i20=YUN5_-FSnWg@mail.gmail.com>
2023-09-15 11:12 ` Mika Westerberg [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=20230915111225.GQ1599918@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=alex@alexbal.com \
--cc=andreas.noever@gmail.com \
--cc=calvin.walton@kepstin.ca \
--cc=dcb314@hotmail.com \
--cc=kjhambrick@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=michael.jamet@intel.com \
--cc=teslan223@gmail.com \
--cc=wse@tuxedocomputers.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