All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Jesper Krogh <jesper@krogh.cc>,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	Avuton Olrich <avuton@gmail.com>
Subject: Re: Linux 2.6.26-rc5
Date: Mon, 9 Jun 2008 12:01:40 +0200	[thread overview]
Message-ID: <200806091201.41167.elendil@planet.nl> (raw)
In-Reply-To: <200806082139.45829.bjorn.helgaas@hp.com>

On Monday 09 June 2008, Bjorn Helgaas wrote:
> On Saturday 07 June 2008 3:50:59 pm Frans Pop wrote:
> > Jesper Krogh wrote:
> > > Not that they seem critical to the system but I do get alot of
> > > these. I cant remember having seen that before.
> > >
> > > [    2.904467] system 00:06: iomem range 0x0-0x0 could not be reserved 
> > > [    2.904469] system 00:06: iomem range 0x0-0x0 could not be reserved 
> > > [    2.904471] system 00:06: iomem range 0x0-0x0 could not be reserved 
> > > [    2.904473] system 00:06: iomem range 0x0-0x0 could not be reserved
> >
> > I'm getting these too. Not present in the last -rc4 kernel I built.
>
> The patch below should fix this and is already in Linus' tree.
> Can you give it a whirl to confirm?  Thanks!
>
> PNP: skip UNSET MEM resources as well as DISABLED ones
[...]

Yes, that does the trick. Tested using a kernel built from git head.

Thanks,
FJP

  reply	other threads:[~2008-06-09 10:01 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-05  3:36 Linux 2.6.26-rc5 Linus Torvalds
2008-06-05 11:24 ` Olaf Hering
2008-06-05 12:09   ` Linux 2.6.26-rc5 (G5 SATA broken) Hugh Dickins
2008-06-05 12:09     ` Hugh Dickins
2008-06-05 12:54     ` Alan Cox
2008-06-05 12:54       ` Alan Cox
2008-06-05 13:44       ` [PATCH] libata: fix G5 SATA broken on -rc5 Hugh Dickins
2008-06-05 13:44         ` Hugh Dickins
2008-06-05 14:45         ` Olaf Hering
2008-06-05 14:45           ` Olaf Hering
2008-06-06  4:36     ` Linux 2.6.26-rc5 (G5 SATA broken) Benjamin Herrenschmidt
2008-06-06  4:36       ` Benjamin Herrenschmidt
2008-06-05 12:42   ` Linux 2.6.26-rc5 Alan Cox
2008-06-05 12:42     ` Alan Cox
2008-06-05 13:03 ` Alejandro Riveira Fernández
2008-06-05 14:54   ` Linus Torvalds
2008-06-05 15:12     ` Bjorn Helgaas
2008-06-05 16:12     ` Bjorn Helgaas
2008-06-05 16:19       ` Linus Torvalds
2008-06-05 16:32         ` Bjorn Helgaas
2008-06-05 14:43 ` Ben Dooks
2008-06-06 18:35   ` Linus Torvalds
2008-06-10 12:57     ` ACPI pull for 2.6.26? Adrian Bunk
2008-06-10 15:23       ` Len Brown
2008-06-10 15:39         ` Adrian Bunk
2008-06-05 14:47 ` Linux 2.6.26-rc5 Alex Romosan
2008-06-07 19:44 ` Jesper Krogh
2008-06-07 21:50   ` Frans Pop
2008-06-09  3:39     ` Bjorn Helgaas
2008-06-09 10:01       ` Frans Pop [this message]
2008-06-07 19:52 ` Jesper Krogh
  -- strict thread matches above, loose matches on Subject: below --
2008-06-05 15:04 Lior Dotan

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=200806091201.41167.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=avuton@gmail.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=jesper@krogh.cc \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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.