From: Alexey Starikovskiy <astarikovskiy@suse.de>
To: Kevin Hao <kexin.hao@windriver.com>
Cc: ak@linux.intel.com, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH 1/2] fix acpi ec read write bug
Date: Thu, 11 Sep 2008 10:10:41 +0400 [thread overview]
Message-ID: <48C8B661.1030508@suse.de> (raw)
In-Reply-To: <d41e1c0a5be061176c65db7ef42263f75ae84dcb.1221102420.git.kexin.hao@windriver.com>
Kevin Hao wrote:
> Fill in command unit of transaction_data structure, otherwise
> gpe_transaction will skip read or write instruction.
>
> Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
> ---
> drivers/acpi/ec.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/acpi/ec.c b/drivers/acpi/ec.c
> index bd3555c..0c65e82 100644
> --- a/drivers/acpi/ec.c
> +++ b/drivers/acpi/ec.c
> @@ -240,6 +240,7 @@ static int acpi_ec_transaction_unlocked(struct acpi_ec *ec, u8 command,
> }
> atomic_set(&ec->irq_count, 0);
> /* fill in transaction structure */
> + ec->t.command = command;
> ec->t.wdata = wdata;
> ec->t.wlen = wdata_len;
> ec->t.rdata = rdata;
NAK
Command is filled in acpi_ec_write_command() in order to make window between start of
the transaction and validity of the transaction data to the bare minimum.
prev parent reply other threads:[~2008-09-11 6:10 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 ` [PATCH 2/2] fix acpi ec set GPE storm flag bug Kevin Hao
2008-09-11 4:07 ` [PATCH 1/2] fix acpi ec read write bug Zhao Yakui
2008-09-11 4:49 ` Kevin Hao
2008-09-11 5:54 ` Zhao Yakui
2008-09-11 6:10 ` Alexey Starikovskiy [this message]
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=48C8B661.1030508@suse.de \
--to=astarikovskiy@suse.de \
--cc=ak@linux.intel.com \
--cc=kexin.hao@windriver.com \
--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