[<prev] [next>] [day] [month] [year] [list]
Message-ID: <1AE640813FDE7649BE1B193DEA596E88026A46B1@SHSMSX101.ccr.corp.intel.com>
Date: Mon, 24 Nov 2014 02:47:45 +0000
From: "Zheng, Lv" <lv.zheng@...el.com>
To: "Kirill A. Shutemov" <kirill@...temov.name>
CC: "Wysocki, Rafael J" <rafael.j.wysocki@...el.com>,
"Brown, Len" <len.brown@...el.com>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Lv Zheng (zetalog@...il.com)" <zetalog@...il.com>
Subject: RE: [UPDATE RFC PATCH 2] ACPICA: Events: Introduce
ACPI_GPE_HANDLER_RAW to fix 2 issues for the current GPE APIs.
Hi,
Adding people that were disturbed by my fault previously.
You should also reply in the same thread with this validation result.
As we might need this to be the motivation for the proposal that the GPE dead lock issue should be fixed in a higher priority way.
I've reported this at:
https://bugs.acpica.org/show_bug.cgi?id=1100
Thanks and best regards
-Lv
> From: Kirill A. Shutemov [mailto:kirill@...temov.name]
> Sent: Friday, November 21, 2014 8:41 PM
>
> On Fri, Nov 21, 2014 at 01:05:40AM +0000, Zheng, Lv wrote:
> > Hi, Kirill
> >
> > Please help to check again to use the updated patch.
> > Sorry for my mistake.
> >
> > I originally used a patch that will unlock before invoking all handlers.
> > But as requested by maintainers, the new ACPICA part will use a ACPI_GPE_HANDLER_RAW flag, and I updated my patch in a hurry
> for you without updating the ec.c.
> >
> > It's my fault.
> > I can also do some local confirmation before disturbing you.
> > Could you tell me how can I reproduce this?
>
> This one seems works
>
> --
> Kirill A. Shutemov
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists