From: Huang Ying <ying.huang@intel.com>
To: "Xiao, Hui" <hui.xiao@linux.intel.com>,
"lenb@kernel.org" <lenb@kernel.org>
Cc: "Chen, Gong" <gong.chen@intel.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH v2] ACPI, APEI, EINJ, Refine the fix of resource conflict
Date: Tue, 11 Oct 2011 15:01:14 +0800 [thread overview]
Message-ID: <4E93E9BA.3020106@intel.com> (raw)
In-Reply-To: <4E93DF1F.8030004@linux.intel.com>
On 10/11/2011 02:15 PM, Xiao, Hui wrote:
> Current fix for resource conflict is to remove the address region <param1 &
> param2, ~param2+1> from trigger resource, which is highly relies on valid user
> input. This patch is trying to avoid such potential issues by fetching the
> exact address region from trigger action table entry.
>
> v2: minor fixes
>
> Signed-off-by: Xiao, Hui <hui.xiao@linux.intel.com>
Acked-by: Huang Ying <ying.huang@intel.com>
Hi, Len,
Can you merged this patch after my APEI patchset?
Best Regards,
Huang Ying
prev parent reply other threads:[~2011-10-11 7:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 6:15 [PATCH v2] ACPI, APEI, EINJ, Refine the fix of resource conflict Xiao, Hui
2011-10-11 7:01 ` Huang Ying [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=4E93E9BA.3020106@intel.com \
--to=ying.huang@intel.com \
--cc=gong.chen@intel.com \
--cc=hui.xiao@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@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