From: Prarit Bhargava <prarit@redhat.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Yinghai Lu <yinghai@kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
Linux PCI <linux-pci@vger.kernel.org>,
Sarah Sharp <sarah.a.sharp@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: [PATCH 1/2] ACPI / PCI: don't allow PCI devices without irq to be enabled
Date: Thu, 03 Oct 2013 19:58:57 -0400 [thread overview]
Message-ID: <524E04C1.7010605@redhat.com> (raw)
In-Reply-To: <CAErSpo6dmSwcM5ensq1fKL=-mbLNyi9G+U+LPA1P=pP8j9=EoA@mail.gmail.com>
On 08/12/2013 06:32 PM, Bjorn Helgaas wrote:
> On Mon, Aug 12, 2013 at 3:32 PM, Yinghai Lu <yinghai@kernel.org> wrote:
>> On Mon, Aug 12, 2013 at 2:14 PM, Bjorn Helgaas <bhelgaas@google.com> wrote:
>>> On Thu, Aug 8, 2013 at 7:57 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
>>>> On Thursday, August 08, 2013 03:35:13 PM Heikki Krogerus wrote:
>>>>> If there is no ACPI entry for the irq, returning error from
>>>>> acpi_pci_enable_irq() if the irq is 0.
>>>>>
>>>>> Prarit Bhargava reported an issue where he noticed that his
>>>>> Dell PowerEdge 840 has buggy BIOS that does not supply ACPI
>>>>> entries for irq with some devices. That lead into kernel
>>>>> generating a warning "genirq: Flags mismatch irq 0...". This
>>>>> will fix that issue.
>>>>>
>>>>> Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
>>>>> Tested-by: Prarit Bhargava <prarit@redhat.com>
>>>>
>>>> Hi Bjorn,
>>>>
>>>> Any objections to this?
>>>
>>> Acked-by: Bjorn Helgaas <bhelgaas@google.com>
>>
>> some USB3 host controller does not have intx configured, but still
>> work with MSI?
>
> Huh, OK, I take back my ack, at least while we investigate this.
>
Bjorn, as suggested I've opened up a BZ here:
https://bugzilla.kernel.org/show_bug.cgi?id=62521
I've only cc'd yourself and Rafael. Heikki -- I didn't find an account under
your intel.com address ...
P.
next prev parent reply other threads:[~2013-10-03 23:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 12:35 [PATCH 0/2] ACPI: return error in acpi_pci_irq_enable when there is no irq Heikki Krogerus
2013-08-08 12:35 ` [PATCH 1/2] ACPI / PCI: don't allow PCI devices without irq to be enabled Heikki Krogerus
2013-08-08 13:57 ` Rafael J. Wysocki
2013-08-12 21:14 ` Bjorn Helgaas
2013-08-12 21:32 ` Yinghai Lu
2013-08-12 22:32 ` Bjorn Helgaas
2013-08-23 17:00 ` Bjorn Helgaas
2013-10-03 23:58 ` Prarit Bhargava [this message]
2013-08-08 12:35 ` [PATCH 2/2] ACPI / PCI: remove an extra check from acpi_pci_irq_enable() Heikki Krogerus
2013-08-08 13:58 ` Rafael J. Wysocki
2013-08-12 21:15 ` Bjorn Helgaas
2013-09-13 12:52 ` [PATCH 0/2] ACPI: return error in acpi_pci_irq_enable when there is no irq Prarit Bhargava
2013-09-13 23:43 ` Rafael J. Wysocki
2013-09-13 23:55 ` Bjorn Helgaas
2013-09-16 7:40 ` Heikki Krogerus
2013-09-16 10:28 ` Heikki Krogerus
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=524E04C1.7010605@redhat.com \
--to=prarit@redhat.com \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=sarah.a.sharp@linux.intel.com \
--cc=yinghai@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 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).