All of lore.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	tglx@linutronix.de, linux-kernel@vger.kernel.org,
	linux-acpi@vger.kernel.org
Subject: Re: 2.6.25-git: "x86: fix ioremap RAM check" causes - ACPI Error... Could not map memory
Date: Mon, 4 Feb 2008 17:52:30 -0500	[thread overview]
Message-ID: <200802041752.31146.lenb@kernel.org> (raw)
In-Reply-To: <20080204122724.GA31186@elte.hu>

On Monday 04 February 2008 07:27, Ingo Molnar wrote:
> 
> * Ingo Molnar <mingo@elte.hu> wrote:
> 
> > * Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > 
> > > On Monday, 4 of February 2008, Len Brown wrote:
> > > > My HP nx6325 started printing the ACPI Error's below starting at 
> > > > the commit below.
> > > 
> > > Mine too.
> > 
> > does latest x86.git#mm fix it?
> 
> access coordinates:
> 
>   http://people.redhat.com/mingo/x86.git/README
> 
>

I do not see these warnings
in either the master or mm branches of x86.git.

Unless you tell me otherwise, I'm not going to worry about it.

thanks,
-Len

master:

commit 795d45b22c079946332bf3825afefe5a981a97b6
Author: Andrew Morton <akpm@linux-foundation.org>
Date:   Mon Feb 4 16:48:10 2008 +0100

    x86: fix RTC lockdep warning: potential hardirq recursion

mm:

commit b7e245f3a4f80a76a79bcff64319479ff8cd4091
Author: Ingo Molnar <mingo@elte.hu>
Date:   Mon Feb 4 16:48:22 2008 +0100

    pci: pci_enable_device_bars() fix

      reply	other threads:[~2008-02-04 22:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-04  7:28 2.6.25-git: "x86: fix ioremap RAM check" causes - ACPI Error... Could not map memory Len Brown
2008-02-04 12:20 ` Rafael J. Wysocki
2008-02-04 12:25   ` Ingo Molnar
2008-02-04 12:27     ` Ingo Molnar
2008-02-04 22:52       ` 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=200802041752.31146.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --cc=tglx@linutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.