From: Linus Torvalds <torvalds@linux-foundation.org>
To: Andrew Patterson <andrew.patterson@hp.com>
Cc: Matthew Wilcox <matthew@wil.cx>,
Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
jbarnes@virtuousgeek.org
Subject: Re: [PATCH 0/1] Recurse when searching for empty slots in resources trees
Date: Wed, 17 Jun 2009 13:12:42 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0906171309500.16802@localhost.localdomain> (raw)
In-Reply-To: <1245269316.8234.270.camel@bluto.andrew>
On Wed, 17 Jun 2009, Andrew Patterson wrote:
> >
> > This is why I'd really like to see the output of my test-patch. It would
> > show exactly _where_ that resource is inserted, and the whole call-chain.
> >
> > I'm appending a version that only does it for resources that have names
> > starting with "PCI Bus", so it should be less noisy. But again, it's
> > totally untested.
> >
>
> Here you go (I can provide the full boot log if needed). Note, there is
> nothing for c3 here:
Ok, so that means it got inserted into the resource tree some other way
entirely. Or maybe the name got changed after-the-fact. Both of which
imply that something is really really wrong.
The ones your trace _does_ show are the ones that got inserted correctly
and aren't buggy. Can anybody see how that buggy resource got inserted?
Linus
next prev parent reply other threads:[~2009-06-17 20:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 22:04 [PATCH 0/1] Recurse when searching for empty slots in resources trees 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
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 [this message]
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.0906171309500.16802@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=andrew.patterson@hp.com \
--cc=jbarnes@virtuousgeek.org \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
/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