From: Linn Crosetto <linn@hp.com>
To: "Moore, Robert" <robert.moore@intel.com>
Cc: "rjw@sisk.pl" <rjw@sisk.pl>,
"ming.m.lin@intel.com" <ming.m.lin@intel.com>,
"Zheng, Lv" <lv.zheng@intel.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] acpi: remove length check for large registers
Date: Fri, 15 Mar 2013 15:18:45 -0600 [thread overview]
Message-ID: <20130315211845.GD10730@oranje.fc.hp.com> (raw)
In-Reply-To: <94F2FBAB4432B54E8AACC7DFDE6C92E36F489B66@ORSMSX101.amr.corp.intel.com>
On Fri, Mar 15, 2013 at 08:50:45PM +0000, Moore, Robert wrote:
> Can you explain in a bit more detail what brings this up?
>
> I'm aware of the limitation of the generic address structure, but we are forced by the (current) ACPI specification to use it if it is present for a given register.
A system with a GPE block bit_width of 256 triggers it. In this case, the length
check can never succeed.
Thanks,
Linn
next prev parent reply other threads:[~2013-03-15 21:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 19:56 [PATCH] acpi: remove length check for large registers Linn Crosetto
2013-03-15 20:50 ` Moore, Robert
2013-03-15 21:18 ` Linn Crosetto [this message]
2013-03-19 18:48 ` Moore, Robert
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=20130315211845.GD10730@oranje.fc.hp.com \
--to=linn@hp.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=ming.m.lin@intel.com \
--cc=rjw@sisk.pl \
--cc=robert.moore@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