From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Prarit Bhargava <prarit@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Robert Moore <robert.moore@intel.com>,
Lv Zheng <lv.zheng@intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Len Brown <lenb@kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Mario_Limonciello@dell.com, Stable <stable@vger.kernel.org>,
"devel@acpica.org" <devel@acpica.org>
Subject: Re: [PATCH] ACPI: fix Thunderbolt hotplug
Date: Wed, 27 Apr 2016 14:33:48 +0200 [thread overview]
Message-ID: <CAJZ5v0hdnQDZt2ur5R0xVH-985+pj5yQSxRBS+LgJZ_Ykk9Uww@mail.gmail.com> (raw)
In-Reply-To: <1461760019-12930-1-git-send-email-prarit@redhat.com>
On Wed, Apr 27, 2016 at 2:26 PM, Prarit Bhargava <prarit@redhat.com> wrote:
> Rafael, this patch is in the acpica.git tree as 7a3bd2d ("Dispatcher: Update
> thread ID for recursive method calls"). I've had many positive testing
> results from hardware vendors and users with this patch and this resolves
> many of the problems seen here:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=115121
>
> This does not fix the problems with the TB docking station. Although this
> patch will also be required, the docking station issues require a FW update.
> Updated FW should be coming soon to resolve those problems.
Lv is going to send me patches for the current ACPICA release shortly.
I'll pick up this one from that series. Hopefully, that's not a problem.
Thanks,
Rafael
next prev parent reply other threads:[~2016-04-27 12:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 12:26 [PATCH] ACPI: fix Thunderbolt hotplug Prarit Bhargava
2016-04-27 12:33 ` Rafael J. Wysocki [this message]
2016-04-27 13:07 ` Mario_Limonciello
2016-04-27 13:07 ` Mario_Limonciello
2016-04-28 18:38 ` Andy Lutomirski
2016-04-28 18:44 ` Mario_Limonciello
2016-04-28 18:44 ` Mario_Limonciello
2016-04-28 18:46 ` Andy Lutomirski
2016-04-28 18:49 ` Mario_Limonciello
2016-04-28 18:49 ` Mario_Limonciello
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=CAJZ5v0hdnQDZt2ur5R0xVH-985+pj5yQSxRBS+LgJZ_Ykk9Uww@mail.gmail.com \
--to=rafael@kernel.org \
--cc=Mario_Limonciello@dell.com \
--cc=devel@acpica.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=prarit@redhat.com \
--cc=rafael.j.wysocki@intel.com \
--cc=robert.moore@intel.com \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.