Re: [Astlinux-devel] Updating other devices in trunk

Darrick Hartman wrote:
> Philip Prindeville wrote:
>   
>> Kristian Kielhofner wrote:
>>     
>>> On Fri, Nov 7, 2008 at 5:34 PM, Philip Prindeville
>>> <phi...@re...> wrote:
>>>   
>>>       
>>>> That's right.
>>>>
>>>> We've got a fair amount of churn on some files (like the OCF patches and
>>>> the net5501/linux.config file) and what that to stabilize before we
>>>> figure out what really got changed.
>>>>
>>>>
>>>>     
>>>>         
>>> So what is the deal with OCF...
>>>
>>> It looks like we've got a minimal OCF patch in device/kernel-patches.
>>>
>>> We also (attempt) to untar an OCF tarball into the kernel source.
>>>
>>> Why not just apply a straight OCF patch?  Why the untar?  This was
>>> brought to my attention because as-is, it's broken either way.  We're
>>> not currently passing "z" to the tar command line to pipe it through
>>> gzip first.  That got me to thinking - what *should* we be doing here?
>>>
>>>   
>>>       
>> OCF isn't part of the kernel, it comes as a separate tarball.  It gets 
>> unpacked into the kernel (at least until it becomes part of the kernel 
>> and we can retire the tarball and makefile-glue).
>>
>> The patch gets applied is a minor patch to the kernel Kconfig and 
>> Makefiles to include the tarballed directories into the build process... 
>> plus a kind of gross patch for driver/char/random.h... which is 
>> necessary for FIPS RNG conformance testing (i.e. that the RNG has to be 
>> sufficiently R to be strong).
>>
>> I'll commit a fix for two things (the compression included) shortly...
>>     
>
> Kris already committed the fix.
>
> Darrick
>   

Sigh.

Too late.

Anyone know why sourceforge is taking 40+ minutes to send the emails out 
about commits?

-Philip