From: Linus Torvalds <torvalds@linux-foundation.org>
To: Andrew Patterson <andrew.patterson@hp.com>
Cc: linux-pci@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
jbarnes@virtuousgeek.org,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Subject: Re: [PATCH 0/1] Recurse when searching for empty slots in resources trees
Date: Tue, 16 Jun 2009 21:19:11 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0906162116280.16802@localhost.localdomain> (raw)
In-Reply-To: <1245208744.19708.243.camel@grinch>
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
next prev parent reply other threads:[~2009-06-17 4:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 22:04 Andrew Patterson
2009-06-16 22:04 ` [PATCH] " Andrew Patterson
2009-06-16 22:19 ` [PATCH 0/1] " Linus Torvalds
2009-06-16 22:51 ` Andrew Patterson
2009-06-16 23:05 ` Linus Torvalds
2009-06-16 23:32 ` Linus Torvalds
2009-06-17 14:45 ` Ivan Kokshaysky
2009-06-17 16:28 ` Linus Torvalds
2009-06-16 23:38 ` Andrew Patterson
2009-06-16 23:56 ` Linus Torvalds
2009-06-17 0:19 ` Linus Torvalds
2009-06-17 1:04 ` Linus Torvalds
2009-06-17 3:19 ` Andrew Patterson
2009-06-17 4:19 ` Linus Torvalds [this message]
2009-06-17 0:28 ` Jesse Barnes
2009-06-17 16:03 ` Alex Chiang
2009-06-17 9:13 ` Kenji Kaneshige
2009-06-17 13:43 ` Matthew Wilcox
2009-06-17 16:23 ` Linus Torvalds
2009-06-17 17:42 ` Andrew Patterson
2009-06-17 18:12 ` Linus Torvalds
2009-06-17 20:08 ` Andrew Patterson
2009-06-17 20:12 ` Linus Torvalds
2009-06-17 20:17 ` Matthew Wilcox
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=alpine.LFD.2.01.0906162116280.16802@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=andrew.patterson@hp.com \
--cc=ink@jurassic.park.msu.ru \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome