From: Kevin Hao <kexin.hao@windriver.com>
To: ak@linux.intel.com, astarikovskiy@suse.de,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: [PATCH 2/2] fix acpi ec set GPE storm flag bug
Date: Thu, 11 Sep 2008 11:17:45 +0800 [thread overview]
Message-ID: <b1360ffe431c427477d030eb5c182e87f1fcd85a.1221102420.git.kexin.hao@windriver.com> (raw)
In-Reply-To: <d41e1c0a5be061176c65db7ef42263f75ae84dcb.1221102420.git.kexin.hao@windriver.com>
In-Reply-To: <d41e1c0a5be061176c65db7ef42263f75ae84dcb.1221102420.git.kexin.hao@windriver.com>
The intent of the code was clear, however the missing braces
meant that EC_FLAGS_GPE_STORM was incorrectly being set
all the time
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
---
drivers/acpi/ec.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/drivers/acpi/ec.c b/drivers/acpi/ec.c
index 0c65e82..d8f273d 100644
--- a/drivers/acpi/ec.c
+++ b/drivers/acpi/ec.c
@@ -268,9 +268,10 @@ end:
/* it is safe to enable GPE outside of transaction */
acpi_enable_gpe(NULL, ec->gpe, ACPI_NOT_ISR);
} else if (test_bit(EC_FLAGS_GPE_MODE, &ec->flags) &&
- atomic_read(&ec->irq_count) > ACPI_EC_STORM_THRESHOLD)
+ atomic_read(&ec->irq_count) > ACPI_EC_STORM_THRESHOLD) {
pr_debug(PREFIX "GPE storm detected\n");
set_bit(EC_FLAGS_GPE_STORM, &ec->flags);
+ }
return 0;
}
--
1.5.6.2.220.g44701
next prev parent reply other threads:[~2008-09-11 3:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 3:17 [PATCH 0/2]linux-next: fix two bugs in ACPI EC driver Kevin Hao
2008-09-11 3:17 ` [PATCH 1/2] fix acpi ec read write bug Kevin Hao
2008-09-11 3:17 ` Kevin Hao [this message]
2008-09-11 4:07 ` Zhao Yakui
2008-09-11 4:49 ` Kevin Hao
2008-09-11 5:54 ` Zhao Yakui
2008-09-11 6:10 ` Alexey Starikovskiy
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=b1360ffe431c427477d030eb5c182e87f1fcd85a.1221102420.git.kexin.hao@windriver.com \
--to=kexin.hao@windriver.com \
--cc=ak@linux.intel.com \
--cc=astarikovskiy@suse.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®