From: Rene Herman <rene.herman@keyaccess.nl>
To: Fabio Comolli <fabio.comolli@gmail.com>
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 10:01:04 +0200 [thread overview]
Message-ID: <4886E540.2070106@keyaccess.nl> (raw)
In-Reply-To: <b637ec0b0807230017w39ecd5bapc9a6afe29a39d5f3@mail.gmail.com>
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
next prev parent reply other threads:[~2008-07-23 7:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 18:56 New conflict message in latest GIT 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 [this message]
2008-07-23 18:11 ` Fabio Comolli
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=4886E540.2070106@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=fabio.comolli@gmail.com \
--cc=linux-kernel@vger.kernel.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.