From: Lin Ming <ming.m.lin@intel.com>
To: Luca Tettamanti <kronos.it@gmail.com>
Cc: "Moore, Robert" <robert.moore@intel.com>,
Jean Delvare <khali@linux-fr.org>,
Nikolay Mikov <nik.mikov@gmail.com>, Thomas <trenn@suse.de>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
lenb <lenb@kernel.org>
Subject: Re: [BUG] ACPI resource validation not working [Was: Re: ITE 8728F]
Date: Tue, 13 Dec 2011 10:01:22 +0800 [thread overview]
Message-ID: <1323741682.17515.20.camel@minggr> (raw)
In-Reply-To: <CAKPcRGokqQ=jRXkhFdXM7zSGowJ5oWjY7fv+mbz4QtscOX3Ukw@mail.gmail.com>
On Mon, 2011-12-12 at 20:52 +0800, Luca Tettamanti wrote:
> On Fri, Dec 9, 2011 at 3:01 AM, Lin Ming <ming.m.lin@intel.com> wrote:
> > Hi Luca,
> >
> > We have investigated this issue more and think that it's better to move
> > the resource validation code into ACPICA core.
> >
> > Here is the new patch.
> >
> > The major changes include:
> > - Remove acpi_os_validate_address/acpi_os_invalidate_address from osl.c.
> > They are reimplemented in ACPICA core:
> > acpi_ut_add_address_range/acpi_ut_remove_address_range.
> >
> > - Add new interface for drivers to check resource conflict:
> > acpi_check_address_range
> >
> > Could you help to test it?
>
> Sure, works fine:
> Tested-by: Luca Tettamanti <kronos.it@gmail.com>
Thanks.
prev parent reply other threads:[~2011-12-13 2:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 20:53 [BUG] ACPI resource validation not working [Was: Re: ITE 8728F] Luca Tettamanti
2011-11-28 22:56 ` Moore, Robert
2011-11-29 1:48 ` Lin Ming
2011-11-29 13:18 ` Luca Tettamanti
2011-11-29 13:44 ` Lin Ming
2011-11-30 9:07 ` Jean Delvare
2011-12-09 2:01 ` Lin Ming
2011-12-12 9:37 ` Jean Delvare
2011-12-12 12:42 ` Lin Ming
2011-12-12 20:12 ` Jean Delvare
2012-01-11 13:01 ` Jean Delvare
2011-12-12 12:52 ` Luca Tettamanti
2011-12-13 2:01 ` Lin Ming [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=1323741682.17515.20.camel@minggr \
--to=ming.m.lin@intel.com \
--cc=khali@linux-fr.org \
--cc=kronos.it@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=nik.mikov@gmail.com \
--cc=robert.moore@intel.com \
--cc=trenn@suse.de \
/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