From: Len Brown <lenb@kernel.org>
To: Andi Kleen <ak@linux.intel.com>
Cc: Myron Stowe <myron.stowe@hp.com>,
linux-acpi@vger.kernel.org, ying.huang@intel.com
Subject: Re: [PATCH 0/7] ACPI: Memory Mapped I/O (MMIO) pre-mapping
Date: Wed, 27 Oct 2010 21:53:09 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.1010272147110.7501@localhost.localdomain> (raw)
In-Reply-To: <20101025183452.GA3527@gargoyle.fritz.box>
> On Sun, Oct 24, 2010 at 11:38:22PM -0400, Len Brown wrote:
> > applied to acpi-test
> >
> > My comfort-level with these changes is not high.
> >
> > I'm open to your recommendations on if they are
> > too late/risky for this merge window -- or too
> > important to miss this merge window.
>
> The NMI handling is fairly important by itself,
> on the other hand it has been broken for a long time.
>
> But yes the patches were late unfortunately.
>
> I still think it would be better to push them out
> earlier than later simply to get more testing
> on more systems. That's essentially what they need
> and unfortunately the only really good way to get
> that is being part of a release.
I agree with Andi.
This bit is upstream now.
if we have troubles with it, then we can
still revert/repair during 2.6.37 rc.
thanks,
Len Brown, Intel Open Source Technology Center
prev parent reply other threads:[~2010-10-28 1:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 20:23 [PATCH 0/7] ACPI: Memory Mapped I/O (MMIO) pre-mapping Myron Stowe
2010-10-21 20:23 ` [PATCH 1/7] ACPI: Fix ioremap size for MMIO reads and writes Myron Stowe
2010-10-21 20:23 ` [PATCH 2/7] ACPI: Maintain a list of ACPI memory mapped I/O remappings Myron Stowe
2010-10-21 20:23 ` [PATCH 3/7] ACPI: Add interfaces for ioremapping/iounmapping ACPI registers Myron Stowe
2010-10-21 20:24 ` [PATCH 4/7] ACPI: Pre-map 'system event' related register blocks Myron Stowe
2010-10-21 20:24 ` [PATCH 5/7] ACPI: Convert simple locking to RCU based locking Myron Stowe
2010-10-21 20:24 ` [PATCH 6/7] ACPI: Page based coalescing of I/O remappings optimization Myron Stowe
2010-10-22 1:03 ` Huang Ying
2010-10-22 3:23 ` Myron Stowe
2010-10-22 5:17 ` Huang Ying
2010-10-22 16:27 ` Myron Stowe
2010-10-25 1:22 ` Huang Ying
2010-10-21 20:24 ` [PATCH 7/7] ACPI: Re-factor and remove ./drivers/acpi/atomicio.[ch] Myron Stowe
2010-10-22 2:43 ` [PATCH 0/7] ACPI: Memory Mapped I/O (MMIO) pre-mapping Shaohua Li
2010-10-22 2:57 ` Huang Ying
2010-10-22 3:16 ` Shaohua Li
2010-10-22 3:24 ` Huang Ying
2010-10-22 17:10 ` Bjorn Helgaas
2010-10-25 8:34 ` Andi Kleen
2010-10-25 8:43 ` Huang Ying
2010-10-25 9:29 ` Andi Kleen
2010-10-25 3:38 ` Len Brown
2010-10-25 15:34 ` Myron Stowe
2010-10-25 18:34 ` Andi Kleen
2010-10-28 1:53 ` Len Brown [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=alpine.LFD.2.00.1010272147110.7501@localhost.localdomain \
--to=lenb@kernel.org \
--cc=ak@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=myron.stowe@hp.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