From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Linuxppc-dev Development <linuxppc-dev@ozlabs.org>
Subject: Re: pci32 code - early_*config*
Date: Fri, 17 Apr 2009 09:25:59 +0200 [thread overview]
Message-ID: <1239953159.7443.33.camel@pasglop> (raw)
In-Reply-To: <8393884A-D1B0-4081-980C-CF464A38FD6C@kernel.crashing.org>
On Wed, 2009-04-15 at 01:17 -0500, Kumar Gala wrote:
> Ben,
>
> I was looking at what I need to get some additional bits of PCI code
> building w/your ppc64 booke patches. One thing it looks like we need
> is the early config cycle code. The question I have is do we think we
> still need the null_ops support? Also do we think we every get called
> with a NULL hose?
>
> This is fake_pci_bus() in arch/powerpc/kernel/pci_32.c
Hrm.
I'm not fan of the early config stuff, remind me why we need it ?
Ben.
next prev parent reply other threads:[~2009-04-17 7:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 6:17 pci32 code - early_*config* Kumar Gala
2009-04-17 7:25 ` Benjamin Herrenschmidt [this message]
2009-04-17 8:03 ` Roderick Colenbrander
2009-04-17 8:33 ` Benjamin Herrenschmidt
2009-04-17 14:08 ` Kumar Gala
2009-04-17 17:05 ` Benjamin Herrenschmidt
2009-04-17 17:38 ` Kumar Gala
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=1239953159.7443.33.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).