Re: Possible regression caused by commit a192aa923b66a

On Wed, Jun 13, 2018 at 4:45 AM, Kai Heng Feng wrote: > Hi Rafael, > >> On Jun 12, 2018, at 5:17 PM, Rafael J. Wysocki wrote: >> >> On Monday, June 11, 2018 11:52:34 PM CEST Rafael J. Wysocki wrote: >>> >>> --703623056e64c488 >>> Content-Type: text/plain; charset="UTF-8" >>> >>> On

Re: Possible regression caused by commit a192aa923b66a

On Wed, Jun 13, 2018 at 4:45 AM, Kai Heng Feng wrote: > Hi Rafael, > >> On Jun 12, 2018, at 5:17 PM, Rafael J. Wysocki wrote: >> >> On Monday, June 11, 2018 11:52:34 PM CEST Rafael J. Wysocki wrote: >>> >>> --703623056e64c488 >>> Content-Type: text/plain; charset="UTF-8" >>> >>> On

Re: Possible regression caused by commit a192aa923b66a

Hi Rafael, On Jun 12, 2018, at 5:17 PM, Rafael J. Wysocki wrote: On Monday, June 11, 2018 11:52:34 PM CEST Rafael J. Wysocki wrote: --703623056e64c488 Content-Type: text/plain; charset="UTF-8" On Mon, Jun 11, 2018 at 10:09 AM, Rafael J. Wysocki wrote: On Mon, Jun 11, 2018 at

Re: Possible regression caused by commit a192aa923b66a

Hi Rafael, On Jun 12, 2018, at 5:17 PM, Rafael J. Wysocki wrote: On Monday, June 11, 2018 11:52:34 PM CEST Rafael J. Wysocki wrote: --703623056e64c488 Content-Type: text/plain; charset="UTF-8" On Mon, Jun 11, 2018 at 10:09 AM, Rafael J. Wysocki wrote: On Mon, Jun 11, 2018 at

Re: Possible regression caused by commit a192aa923b66a

On Monday, June 11, 2018 11:52:34 PM CEST Rafael J. Wysocki wrote: > > --703623056e64c488 > Content-Type: text/plain; charset="UTF-8" > > On Mon, Jun 11, 2018 at 10:09 AM, Rafael J. Wysocki wrote: > > On Mon, Jun 11, 2018 at 8:26 AM, Kai-Heng Feng > > wrote: > >> Hi Rafael, > >> >

Re: Possible regression caused by commit a192aa923b66a

On Monday, June 11, 2018 11:52:34 PM CEST Rafael J. Wysocki wrote: > > --703623056e64c488 > Content-Type: text/plain; charset="UTF-8" > > On Mon, Jun 11, 2018 at 10:09 AM, Rafael J. Wysocki wrote: > > On Mon, Jun 11, 2018 at 8:26 AM, Kai-Heng Feng > > wrote: > >> Hi Rafael, > >> >

Re: Possible regression caused by commit a192aa923b66a

On Mon, Jun 11, 2018 at 10:09 AM, Rafael J. Wysocki wrote: > On Mon, Jun 11, 2018 at 8:26 AM, Kai-Heng Feng > wrote: >> Hi Rafael, >> >> There's a regression report [1] that says commit a192aa923b66a ("ACPI / >> LPSS: Consolidate runtime PM and system sleep handling") is the first bad >> commit.

Re: Possible regression caused by commit a192aa923b66a

On Mon, Jun 11, 2018 at 10:09 AM, Rafael J. Wysocki wrote: > On Mon, Jun 11, 2018 at 8:26 AM, Kai-Heng Feng > wrote: >> Hi Rafael, >> >> There's a regression report [1] that says commit a192aa923b66a ("ACPI / >> LPSS: Consolidate runtime PM and system sleep handling") is the first bad >> commit.

Re: Possible regression caused by commit a192aa923b66a

On Mon, Jun 11, 2018 at 8:26 AM, Kai-Heng Feng wrote: > Hi Rafael, > > There's a regression report [1] that says commit a192aa923b66a ("ACPI / > LPSS: Consolidate runtime PM and system sleep handling") is the first bad > commit. > > From the looks of it, it didn't introduce any behavioral change.

Re: Possible regression caused by commit a192aa923b66a

On Mon, Jun 11, 2018 at 8:26 AM, Kai-Heng Feng wrote: > Hi Rafael, > > There's a regression report [1] that says commit a192aa923b66a ("ACPI / > LPSS: Consolidate runtime PM and system sleep handling") is the first bad > commit. > > From the looks of it, it didn't introduce any behavioral change.

Possible regression caused by commit a192aa923b66a

Hi Rafael, There's a regression report [1] that says commit a192aa923b66a ("ACPI / LPSS: Consolidate runtime PM and system sleep handling") is the first bad commit. From the looks of it, it didn't introduce any behavioral change. So your help is appreciated. [1]

Possible regression caused by commit a192aa923b66a

Hi Rafael, There's a regression report [1] that says commit a192aa923b66a ("ACPI / LPSS: Consolidate runtime PM and system sleep handling") is the first bad commit. From the looks of it, it didn't introduce any behavioral change. So your help is appreciated. [1]