From: Prarit Bhargava <prarit@redhat.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
linux-acpi@vger.kernel.org, Len Brown <lenb@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Myron Stowe <mstowe@redhat.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] acpi, acpi_pci_irq_enable must return an error if ACPI cannot map an IRQ.
Date: Wed, 07 Aug 2013 08:39:02 -0400 [thread overview]
Message-ID: <52023FE6.9010503@redhat.com> (raw)
In-Reply-To: <86005101.W2j5ifU8yA@vostro.rjw.lan>
On 08/06/2013 06:44 PM, Rafael J. Wysocki wrote:
> On Tuesday, August 06, 2013 10:37:52 AM Prarit Bhargava wrote:
>> On 08/05/2013 10:04 AM, Heikki Krogerus wrote:
>>> Hi,
>>>
>>> On Mon, Aug 05, 2013 at 03:30:16PM +0200, Rafael J. Wysocki wrote:
>>>> On Sunday, August 04, 2013 07:35:37 PM Prarit Bhargava wrote:
>>>>> Hey Rafael,
>>>>>
>>>>> I know you're busy but I was just wondering if this was queued up anywhere or if
>>>>> you had any other questions?
>>>>
>>>> Should be qeued up for 3.12 (currently in linux-next).
>>>
>>> This breaks my xHCI :(
>>>
>>> If the issues is that you are not getting any interrupt, then should
>>> it not be checked separately and only fail in that case? I'm attaching
>>> a patch that I made on top of linux-next, where I do just that. Would
>>> that work for you?
>>>
>>
>> Testing this right now ... I'll get back to everyone when I have results.
>
> In the meantime I've dropped that commit from linux-next as it caused the xHCI
> breakage to happen.
Thanks Rafael.
Heikki, I tested your patch and found that it solves my problem. Sorry for the
breakage :(
Can you add a
Tested-by: Prarit Bhargava <prarit@redhat.com>
to your patch?
Thanks,
P.
next prev parent reply other threads:[~2013-08-07 12:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 14:57 [PATCH] acpi, acpi_pci_irq_enable must return an error if ACPI cannot map an IRQ Prarit Bhargava
2013-07-24 23:35 ` Rafael J. Wysocki
2013-07-25 0:01 ` Prarit Bhargava
2013-07-25 9:57 ` Prarit Bhargava
2013-07-25 12:10 ` Rafael J. Wysocki
2013-08-04 23:35 ` Prarit Bhargava
2013-08-05 13:30 ` Rafael J. Wysocki
2013-08-05 14:04 ` Heikki Krogerus
2013-08-06 14:37 ` Prarit Bhargava
2013-08-06 22:44 ` Rafael J. Wysocki
2013-08-07 12:39 ` Prarit Bhargava [this message]
2013-08-07 13:29 ` Heikki Krogerus
2013-08-07 23:04 ` Rafael J. Wysocki
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=52023FE6.9010503@redhat.com \
--to=prarit@redhat.com \
--cc=bhelgaas@google.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mstowe@redhat.com \
--cc=rjw@sisk.pl \
/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.