public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Lin Ming <ming.m.lin@intel.com>
Cc: Luca Tettamanti <kronos.it@gmail.com>,
	"Moore, Robert" <robert.moore@intel.com>,
	Nikolay Mikov <nik.mikov@gmail.com>, Thomas <trenn@suse.de>,
	linux-acpi@vger.kernel.org, lenb <lenb@kernel.org>
Subject: Re: [BUG] ACPI resource validation not working [Was: Re: ITE 8728F]
Date: Mon, 12 Dec 2011 21:12:45 +0100	[thread overview]
Message-ID: <20111212211245.67baf2b1@endymion.delvare> (raw)
In-Reply-To: <CAF1ivSaN6V5tz6ttUL9_1htFjVX8qEVv-eCq04s=_nPAaDMH6g@mail.gmail.com>

On Mon, 12 Dec 2011 20:42:50 +0800, Lin Ming wrote:
> On Mon, Dec 12, 2011 at 5:37 PM, Jean Delvare <khali@linux-fr.org> wrote:
> > I have no objection for an upstream patch, but the main problem we have
> > at the moment is with already released kernels. Versions 2.6.39, 3.0
> > and 3.1 currently have a regression as the ACPI resource conflict
> > checks are inefficient, and this allows conflicting drivers to be
> > loaded together. So you are free to reimplement things differently in
> > version 3.2 and later, but for these 3 older versions we need the
> > smallest possible patch, so that it is accepted in stable branches.
> >
> > In other words, I would like two patches, one just adding back the code
> > that was accidentally dropped, and a second one moving things around if
> > you think it makes sense (and I tend to agree.) That way we can easily
> > backport only the first patch to kernel versions 2.6.39 to 3.1.
> 
> Sure.
> 
> I have send out the patch.
> 
> [PATCH] ACPICA: Put back the call to acpi_os_validate_address
> http://marc.info/?l=linux-acpi&m=132257617527119&w=2

Perfect, thank you!

-- 
Jean Delvare

  reply	other threads:[~2011-12-12 20:13 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 [this message]
2012-01-11 13:01               ` Jean Delvare
2011-12-12 12:52         ` Luca Tettamanti
2011-12-13  2:01           ` Lin Ming

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=20111212211245.67baf2b1@endymion.delvare \
    --to=khali@linux-fr.org \
    --cc=kronos.it@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=ming.m.lin@intel.com \
    --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