From: Chen Gong <gong.chen@linux.intel.com>
To: Chen Gong <gong.chen@linux.intel.com>
Cc: tony.luck@intel.com, ying.huang@intel.com, lenb@kernel.org,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH v2] ACPI, APEI, EINJ, limit the range of einj_param
Date: Thu, 15 Mar 2012 16:54:24 +0800 [thread overview]
Message-ID: <4F61AE40.1020908@linux.intel.com> (raw)
In-Reply-To: <1330747003-11891-1-git-send-email-gong.chen@linux.intel.com>
On 3/3/2012 11:56 AM, Chen Gong wrote:
> On the platforms with ACPI4.x support, parameter extension
> is not always doable, which means only parameter extension
> is enabled, einj_param can take effect.
>
> v2->v1: stopping early in einj_get_parameter_address for einj_param
>
> Signed-off-by: Chen Gong<gong.chen@linux.intel.com>
> ---
> drivers/acpi/apei/einj.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/acpi/apei/einj.c b/drivers/acpi/apei/einj.c
> index 4ca087d..3d3816f 100644
> --- a/drivers/acpi/apei/einj.c
> +++ b/drivers/acpi/apei/einj.c
> @@ -238,7 +238,7 @@ static void *einj_get_parameter_address(void)
> return v5param;
> }
> }
> - if (paddrv4) {
> + if (param_extension&& paddrv4) {
> struct einj_parameter *v4param;
>
> v4param = acpi_os_map_memory(paddrv4, sizeof(*v4param));
Hi, Len
Any comment for this?
next prev parent reply other threads:[~2012-03-15 8:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 8:44 [PATCH] ACPI, APEI, EINJ, limit the range of einj_param Chen Gong
2012-02-28 8:54 ` Huang Ying
2012-02-28 18:33 ` Luck, Tony
2012-02-29 2:44 ` Chen Gong
2012-02-29 19:34 ` Luck, Tony
2012-03-02 6:54 ` Chen Gong
2012-03-02 19:42 ` Luck, Tony
2012-03-03 3:56 ` [PATCH v2] " Chen Gong
2012-03-15 8:54 ` Chen Gong [this message]
2012-03-15 16:48 ` Luck, Tony
2012-03-16 5:41 ` Chen Gong
2012-02-29 5:38 ` [PATCH] " Huang Ying
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=4F61AE40.1020908@linux.intel.com \
--to=gong.chen@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=ying.huang@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).