linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 19/20] [POWERPC] pci32: 4xx embedded platforms want to reassign all PCI resources
Date: Fri, 14 Dec 2007 07:37:23 +1100	[thread overview]
Message-ID: <1197578243.15741.150.camel@pasglop> (raw)
In-Reply-To: <20071213130113.59342c40@weaponx>


> This one is slightly broken in my opinion.  You've added
> the ppc_pci_flags to all of these platforms, which is fine for your
> intended goal.  But now all of these platforms _have_ to compile with
> PCI enabled or they'll break with:
> 
> arch/powerpc/platforms/built-in.o: In function `walnut_probe':
> walnut.c:(.init.text+0x9a): undefined reference to `ppc_pci_flags'
> walnut.c:(.init.text+0xa6): undefined reference to `ppc_pci_flags'
> make[1]: *** [.tmp_vmlinux1] Error 1
> 
> So to do it correctly we need to either select CONFIG_PCI for all of
> them, wrap the ppc_pci_flags assignment in #ifdef CONFIG_PCI, or move
> the ppc_pci_flags variable declaration into something that always gets
> compiled.

Hrm... PCI is user selectable ? Forgot about that ...

All those platforms have PCI slots, so we may as well select it in
Kconfig... I'd rather avoid #ifdef's

Ben.

  reply	other threads:[~2007-12-13 20:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-13  7:38 [PATCH 19/20] [POWERPC] pci32: 4xx embedded platforms want to reassign all PCI resources Benjamin Herrenschmidt
2007-12-13  9:42 ` Stefan Roese
2007-12-13  9:56   ` Stefan Roese
2007-12-13 11:12   ` Benjamin Herrenschmidt
2007-12-13 19:01 ` Josh Boyer
2007-12-13 20:37   ` Benjamin Herrenschmidt [this message]
2007-12-13 20:40     ` Josh Boyer
2007-12-13 20:52       ` Benjamin Herrenschmidt
2007-12-13 21:11         ` Josh Boyer
2007-12-13 21:37           ` Benjamin Herrenschmidt
2007-12-13 21:59             ` Josh Boyer
2007-12-14  5:48               ` Stefan Roese
2007-12-13 19:05 ` Josh Boyer
2007-12-13 20:37   ` Benjamin Herrenschmidt

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=1197578243.15741.150.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=jwboyer@linux.vnet.ibm.com \
    --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).