mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Fabio Comolli" <fabio.comolli@gmail.com>
To: "Rene Herman" <rene.herman@keyaccess.nl>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Andrew Morton" <akpm@osdl.org>,
	"Bjorn Helgaas" <bjorn.helgaas@hp.com>
Subject: Re: New conflict message in latest GIT
Date: Wed, 23 Jul 2008 20:11:47 +0200	[thread overview]
Message-ID: <b637ec0b0807231111o133ad391k79acceb777c2e7a6@mail.gmail.com> (raw)
In-Reply-To: <4886E540.2070106@keyaccess.nl>

Hi Rene.
I can only confirm that Linus' tree  2.6.26-06077-gc010b2f
(commit c010b2f... Merge
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6)
shows the message.

Grepping the file you suggested gives:

fcomolli@hawking:~/software/GIT-TREES/linux-2.6/drivers/pnp> egrep
'RESOURCE_IO|RESOURCE_MEM' quirks.c
		    option->type == IORESOURCE_IO) {
			if (!(pci_resource_flags(pdev, i) & IORESOURCE_MEM) ||
			     (res = pnp_get_resource(dev, IORESOURCE_MEM, j));
fcomolli@hawking:~/software/GIT-TREES/linux-2.6/drivers/pnp>

so both IORESOURCE_IO and IORESOURCE_MEM are present in the file...

But definitely this is Linus' tree.
Cheers,
Fabio

On Wed, Jul 23, 2008 at 10:01 AM, Rene Herman <rene.herman@keyaccess.nl> wrote:
> On 23-07-08 09:17, Fabio Comolli wrote:
>
>>>
>>> http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.26-rc8/2.6.26-rc8-mm1/broken-out/pnp-have-quirk_system_pci_resources-include-io-resources.patch
>>
>> I did not add it manually for sure. By the way, I don't see any ACPI
>> related problems with this kernel.
>
> You can just look at drivers/pnp/quirks.c:quirk_system_pci_resources() and
> see if it's still IORESOURCE_MEM only (current linus) or includes
> IORESOURCE_IO resources as per that patch.
>
> Had a momentary notion that if we specifically exclude ACPI in favour of PCI
> as that patch does this could _cause_ the message -- before, the PCI smbus
> driver just would've failed but perhaps you don't even have such a driver or
> something.
>
> Probably way of base. Just had a deja vu to my own soundcard trouble.
>
> Rene
>

  reply	other threads:[~2008-07-23 18:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-22 18:56 Fabio Comolli
2008-07-22 20:00 ` Rene Herman
2008-07-22 20:14   ` Rene Herman
2008-07-23  7:17     ` Fabio Comolli
2008-07-23  8:01       ` Rene Herman
2008-07-23 18:11         ` Fabio Comolli [this message]
2008-07-23 18:38           ` Rene Herman
2008-07-23 18:56 ` Bjorn Helgaas
2008-07-23 19:50   ` Fabio Comolli
2008-08-09 16:13     ` Jean Delvare
2008-08-09 16:32       ` Fabio Comolli
2008-08-09 17:03         ` Jean Delvare
2008-08-09 18:46           ` Fabio Comolli

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=b637ec0b0807231111o133ad391k79acceb777c2e7a6@mail.gmail.com \
    --to=fabio.comolli@gmail.com \
    --cc=akpm@osdl.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rene.herman@keyaccess.nl \
    /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

all inboxes | Powered by JetHome®