export-objs in spi Makefile broke in latest linuxppc_2_4_deve l [r eposted]?

[Rowan, Chad]

Agreed.

-----Original Message-----
From: Kumar Gala [mailto:galak at kernel.crashing.org] 
Sent: Thursday, July 20, 2006 8:52 AM
To: Rowan, Chad
Cc: hs at denx.de; linuxppc-embedded at ozlabs.org
Subject: Re: export-objs in spi Makefile broke in latest linuxppc_2_4_deve l
[r eposted]?


On Jul 20, 2006, at 8:38 AM, Rowan, Chad wrote:

> Why should this be taken off list?  Is it because it's Denx  
> specific?  Or
> because it's 2.4 specific?  There is active 5200 development on the  
> 2.4
> kernel at Denx and it seems relevant to this list.

Because its Denx specific, I believe the tree you are taking about is  
maintained only by Denx and not a community tree.

- k

> -----Original Message-----
> From: Kumar Gala [mailto:galak at kernel.crashing.org]
> Sent: Thursday, July 20, 2006 8:12 AM
> To: hs at denx.de
> Cc: linuxppc-embedded at ozlabs.org; Chad.Rowan at thyssenkrupp.com
> Subject: Re: export-objs in spi Makefile broke in latest  
> linuxppc_2_4_deve l
> [r eposted]?
>
>
> On Jul 19, 2006, at 11:55 PM, Heiko Schocher wrote:
>
>> Hello Chad
>>
>>> linuxppc_2_4_devel is alive and well.
>>>
>>> http://www.denx.de/cgi-bin/gitweb.cgi?
>>> p=linuxppc_2_4_devel.git;a=shortlog
>>
>> You speak from the DENX linuxppc_2_4_devel Kernel? If so, I think
>> you are right.
>> I had the same problem, some days ago. I made a SPI bitbanging
>> algorithm, but
>> I dont know, if this goes in the git repository from DENX ...
>> Wolfgang?
>
> I think this issue should be taken off list.
>
> - k