From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jin Dongming Subject: Re: [PATCH 4/8] ACPI: Use GPE reference counting to support shared GPEs Date: Fri, 19 Feb 2010 16:24:53 +0900 Message-ID: <4B7E3CC5.9040901@np.css.fujitsu.com> References: <201002172335.47703.rjw@sisk.pl> <201002172341.07353.rjw@sisk.pl> <4B7CE6A3.7020103@np.css.fujitsu.com> <201002182101.44171.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <201002182101.44171.rjw@sisk.pl> Sender: linux-pci-owner@vger.kernel.org To: "Rafael J. Wysocki" Cc: Jesse Barnes , "Moore, Robert" , Len Brown , ACPI Devel Maling List , pm list , Linux PCI , Shaohua Li , Bjorn Helgaas , Oliver Neukum , Matthew Garrett , LKML , Gary Hade List-Id: linux-acpi@vger.kernel.org Hi, Rafael J. Wysocki Rafael J. Wysocki wrote: > On Thursday 18 February 2010, Jin Dongming wrote: >> Hi, Rafael J. Wysocki >>> - /* Update enable mask, but don't enable the HW GPE as of yet */ >>> - >>> - status = acpi_ev_enable_gpe(gpe_event_info, FALSE); > > You could preserve some more context. > >> I think the above line code should be remained. If it is deleted, the exception >> event will be raised on some machine. > > Why would it? The GPE is still disabled at the hardware level at this point. > > Rafael > > I am very sorry for my wrong comment. The GPE is still disabled as you wrote. The error message what I got was not caused by GPE event, it was caused by the "status" variable which had not been deleted on x86-next tree. And it is also deleted at this file. So I don't there is problem here. Best regards, Jin Dongming