From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Greg KH <gregkh@linuxfoundation.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Miles J Penner <miles.j.penner@intel.com>,
John Ronciak <john.ronciak@intel.com>,
Tushar N Dave <tushar.n.dave@intel.com>,
"Kirill A. Shutemov" <kirill@shutemov.name>
Subject: Re: [PATCH 0/3] Thunderbolt workarounds
Date: Thu, 27 Dec 2012 11:33:51 +0200 [thread overview]
Message-ID: <20121227093351.GH20026@intel.com> (raw)
In-Reply-To: <CAErSpo6QWZfZ9YQAXkDOPvqBrwhS4wEzrxiUSAi7myVfoDGaKA@mail.gmail.com>
On Wed, Dec 26, 2012 at 05:50:42PM -0700, Bjorn Helgaas wrote:
> On Thu, Dec 13, 2012 at 12:25 PM, Kirill A. Shutemov
> <kirill.shutemov@linux.intel.com> wrote:
> > From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
> >
> > I had chance to test two PC setups with Thunderbolt: Acer Aspire S5 and
> > Intel DZ77RE-75K motherboard. Unfortunately, both of them are broken in
> > different ways.
> >
> > This patchset contains workarounds for the issues.
> >
> > Kirill A. Shutemov (3):
> > PCI Hotplug: workaround for Thunderbolt on Acer Aspire S5
> > PCI Hotplug: convert acpiphp_hp_work to use delayed work
> > PCI Hotplug: workaround for Thunderbolt on Intel DZ77RE-75K
> > motherboard
> >
> > drivers/pci/hotplug/acpi_pcihp.c | 13 +++++++++++++
> > drivers/pci/hotplug/acpiphp_glue.c | 33 +++++++++++++++++++++++++--------
> > 2 files changed, 38 insertions(+), 8 deletions(-)
>
> I'm ignoring these for now. [1/3] has a hardcoded BIOS path that I
> don't think is the right approach and [3/3] has a timeout issue to be
> addressed. [2/3] might be worthwhile by itself, but I'd rather merge
> a complete solution when it's ready.
OK. We'll rework the series with Kirill and submit a better solution.
prev parent reply other threads:[~2012-12-27 9:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 19:25 [PATCH 0/3] Thunderbolt workarounds Kirill A. Shutemov
2012-12-13 15:31 ` [PATCH 1/3] PCI Hotplug: workaround for Thunderbolt on Acer Aspire S5 Kirill A. Shutemov
2012-12-13 18:44 ` Greg KH
2012-12-13 19:35 ` Kirill A. Shutemov
2012-12-14 0:22 ` Bjorn Helgaas
2012-12-14 10:46 ` Kirill A. Shutemov
2012-12-13 15:31 ` [PATCH 2/3] PCI Hotplug: convert acpiphp_hp_work to use delayed work Kirill A. Shutemov
2012-12-13 15:31 ` [PATCH 3/3] PCI Hotplug: workaround for Thunderbolt on Intel DZ77RE-75K motherboard Kirill A. Shutemov
2012-12-13 18:48 ` Greg KH
2012-12-13 20:08 ` Kirill A. Shutemov
2012-12-13 20:25 ` Yinghai Lu
2012-12-13 20:30 ` Linus Torvalds
2012-12-13 20:49 ` Kirill A. Shutemov
2012-12-13 20:54 ` Linus Torvalds
2012-12-13 22:06 ` Rafael J. Wysocki
2012-12-14 10:34 ` Kirill A. Shutemov
2012-12-27 0:50 ` [PATCH 0/3] Thunderbolt workarounds Bjorn Helgaas
2012-12-27 9:33 ` 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=20121227093351.GH20026@intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=john.ronciak@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=miles.j.penner@intel.com \
--cc=tushar.n.dave@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).