From: Kumar Gala <galak@kernel.crashing.org>
To: David Gibson <dwg@au1.ibm.com>
Cc: "linuxppc-dev@ozlabs.org list" <linuxppc-dev@ozlabs.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: asm-ppc header issues when building ARCH=powerpc
Date: Wed, 22 Aug 2007 22:09:52 -0500 [thread overview]
Message-ID: <4FA0E2BC-BDD3-403F-882F-C2CDEC53BBC8@kernel.crashing.org> (raw)
In-Reply-To: <20070823024937.GD7042@localhost.localdomain>
On Aug 22, 2007, at 9:49 PM, David Gibson wrote:
> On Wed, Aug 22, 2007 at 02:30:47PM -0500, Josh Boyer wrote:
>> On Wed, 22 Aug 2007 10:19:21 -0500
>> Kumar Gala <galak@kernel.crashing.org> wrote:
>>
>>> Guys,
>>>
>>> I was wondering if I could get your help with looking at the
>>> following lists and determining if we have an issue or not related
>>> the following files:
>>>
>>> Getting some classification on these would be good. Possibly
>>> classifications, doesn't build in ARCH=powerpc, remove include, real
>>> issue, etc.
>>
>> Sure.
>>
>>> ./drivers/i2c/busses/i2c-ibm_iic.c:#include <asm/ocp.h>
>>> ./drivers/i2c/busses/i2c-ibm_iic.c:#include <asm/ibm4xx.h>
>>
>> These one depends on IBM_OCP in Kconfig. We don't select/enable
>> that on
>> any existing arch/powerpc 4xx stuff so it won't be built anyway.
>
> Nor will we ever enable IBM_OCP in arch/powerpc: the device tree
> entirely obsoletes the OCP crap.
Agreed. We shouldn't taint arch/powerpc with OCP :)
- k
next prev parent reply other threads:[~2007-08-23 3:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 15:19 asm-ppc header issues when building ARCH=powerpc Kumar Gala
2007-08-22 16:01 ` Scott Wood
2007-08-22 19:30 ` Josh Boyer
2007-08-23 2:49 ` David Gibson
2007-08-23 3:09 ` Kumar Gala [this message]
2007-08-23 2:47 ` David Gibson
2007-08-23 3:22 ` Kumar Gala
2007-08-23 17:33 ` Scott Wood
2007-08-23 18:00 ` Kumar Gala
2007-08-23 3:33 ` Kumar Gala
2007-08-23 3:33 ` David Gibson
2007-08-23 4:16 ` Kumar Gala
2007-08-23 9:47 ` Geert Uytterhoeven
2007-08-23 18:56 ` Brad Boyer
2007-08-24 7:10 ` Geert Uytterhoeven
2007-08-24 7:24 ` Kumar Gala
2007-08-24 7:24 ` Geert Uytterhoeven
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=4FA0E2BC-BDD3-403F-882F-C2CDEC53BBC8@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=dwg@au1.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).