[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.01.0906162116280.16802@localhost.localdomain>
Date: Tue, 16 Jun 2009 21:19:11 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Andrew Patterson <andrew.patterson@...com>
cc: linux-pci@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
jbarnes@...tuousgeek.org,
Ivan Kokshaysky <ink@...assic.park.msu.ru>
Subject: Re: [PATCH 0/1] Recurse when searching for empty slots in resources
trees
On Wed, 17 Jun 2009, Andrew Patterson wrote:
>
> This looks functionally equivalent to the current code.
Absolutely. It's only meant to add the call chains for all the resource
additions, so that we could see how that buggy 'c2' resource gets added as
a parent to 'c3' (when it should be the other way around).
> I get way too much output to be useful. I can log the serial port if we
> need it all, or I can change it to just look at the buses in question if
> desired.
Sure. Or increase CONFIG_LOG_BUF_SHIFT to 22 or somethng insane like that
(so that it logs up to 4MB of messages).
But yeah, if you just make it smarter, and only do that WARN() thing for
resources that match "PCI Bus" at the beginning of the name, that should
be plenty good enough.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists