RE: [PATCH] ACPI: don't show an error when we're not in charge of PCIe hotplug.

2016-06-23 Thread Mario_Limonciello
nel@vger.kernel.org; Len > Brown ; Rafael J. Wysocki > Subject: Re: [PATCH] ACPI: don't show an error when we're not in charge of > PCIe hotplug. > > On Wed, Jun 22, 2016 at 10:53 PM, Andy Lutomirski > wrote: > > On Wed, Jun 22, 2016 at 12:43 PM, wrote: > &

Re: [PATCH] ACPI: don't show an error when we're not in charge of PCIe hotplug.

2016-06-22 Thread Rafael J. Wysocki
On Wed, Jun 22, 2016 at 10:53 PM, Andy Lutomirski wrote: > On Wed, Jun 22, 2016 at 12:43 PM, wrote: >>> -Original Message- >>> From: rjwyso...@gmail.com [mailto:rjwyso...@gmail.com] On Behalf Of [cut] >> I think changing that would help communicate what's going on here and at >> least

Re: [PATCH] ACPI: don't show an error when we're not in charge of PCIe hotplug.

2016-06-22 Thread Andy Lutomirski
Wysocki >> ; ACPI Devel Maling List ; >> Linux Kernel Mailing List ; Len Brown >> ; Rafael J. Wysocki ; Andy Lutomirski >> >> Subject: Re: [PATCH] ACPI: don't show an error when we're not in charge of >> PCIe hotplug. >> >> On Tue, Jun 21,

RE: [PATCH] ACPI: don't show an error when we're not in charge of PCIe hotplug.

2016-06-22 Thread Mario_Limonciello
Mailing List ; Len Brown > ; Rafael J. Wysocki ; Andy Lutomirski > > Subject: Re: [PATCH] ACPI: don't show an error when we're not in charge of > PCIe hotplug. > > On Tue, Jun 21, 2016 at 8:01 PM, wrote: > >> -Original Message- > >> From: Peter Jones

Re: [PATCH] ACPI: don't show an error when we're not in charge of PCIe hotplug.

2016-06-21 Thread Rafael J. Wysocki
gt;> Cc: ACPI Devel Maling List ; Limonciello, Mario >>> ; Linux Kernel Mailing List >> ker...@vger.kernel.org>; Len Brown ; Rafael J . Wysocki >>> ; Andy Lutomirski >>> Subject: Re: [PATCH] ACPI: don't show an error when we're not in charge of >>

Re: [PATCH] ACPI: don't show an error when we're not in charge of PCIe hotplug.

2016-06-21 Thread Rafael J. Wysocki
ailing List > ker...@vger.kernel.org>; Len Brown ; Rafael J . Wysocki >> ; Andy Lutomirski >> Subject: Re: [PATCH] ACPI: don't show an error when we're not in charge of >> PCIe hotplug. >> >> (Sorry for the slow response - it's deadline time over here

Re: [PATCH] ACPI: don't show an error when we're not in charge of PCIe hotplug.

2016-06-21 Thread Andy Lutomirski
ailing List > ker...@vger.kernel.org>; Len Brown ; Rafael J . Wysocki >> ; Andy Lutomirski >> Subject: Re: [PATCH] ACPI: don't show an error when we're not in charge of >> PCIe hotplug. >> >> (Sorry for the slow response - it's deadline time over here

RE: [PATCH] ACPI: don't show an error when we're not in charge of PCIe hotplug.

2016-06-21 Thread Mario_Limonciello
i > ; Andy Lutomirski > Subject: Re: [PATCH] ACPI: don't show an error when we're not in charge of > PCIe hotplug. > > (Sorry for the slow response - it's deadline time over here.) > > On Thu, Jun 16, 2016 at 04:56:57PM +0200, Rafael J. Wysocki wrote: > &

Re: [PATCH] ACPI: don't show an error when we're not in charge of PCIe hotplug.

2016-06-21 Thread Peter Jones
(Sorry for the slow response - it's deadline time over here.) On Thu, Jun 16, 2016 at 04:56:57PM +0200, Rafael J. Wysocki wrote: > On Thu, Jun 16, 2016 at 2:12 AM, Rafael J. Wysocki wrote: > > On Thu, Jun 16, 2016 at 12:15 AM, Peter Jones wrote: > >> Right now when booting, on many laptops the f

Re: [PATCH] ACPI: don't show an error when we're not in charge of PCIe hotplug.

2016-06-16 Thread Rafael J. Wysocki
On Thu, Jun 16, 2016 at 2:12 AM, Rafael J. Wysocki wrote: > On Thu, Jun 16, 2016 at 12:15 AM, Peter Jones wrote: >> Right now when booting, on many laptops the firmware manages the PCIe >> bus. As a result, when we call the _OSC ACPI method, it returns an >> error code. Unfortunately the errors

Re: [PATCH] ACPI: don't show an error when we're not in charge of PCIe hotplug.

2016-06-15 Thread Rafael J. Wysocki
On Thu, Jun 16, 2016 at 12:15 AM, Peter Jones wrote: > Right now when booting, on many laptops the firmware manages the PCIe > bus. As a result, when we call the _OSC ACPI method, it returns an > error code. Unfortunately the errors are not very articulate. What exactly do you mean here? > As