[Maverick] [Pull for ti-omap4]: update to TI July OMAP kernel release L24.8 (try #2)

[Bryan Wu]

On 07/29/2010 04:04 AM, Tim Gardner wrote:
> On 07/28/2010 09:34 AM, Bryan Wu wrote:
>> This update includes more than 220 patches which are from TI latest
>> July OMAP
>> kernel release L24.8. Although it is still based on 2.6.34 kernel, it
>> fixed
>> lots of bugs, updated syslink driver, imported some ARM common fixes
>> and added
>> support for new ES2.0 hardware.
>>
>> I tested on my OMAP4 based Panda board, it is more stable than before.
>> Kernel
>> oops about bad_pages was gone. Tried to update to latest Ubuntu
>> Maverick and
>> didn't see any kernel series oops as before.
>> BugLink: http://bugs.launchpad.net/bugs/605739
>>
>> I fixed lots of coding sytle issues, but I still keep some warning and
>> errors
>> there:
>>   - warning (line over 80 characters): keep them for header files, macros
>>   - 2 errors ("foo * bar" should be "foo *bar") are checkpatch.pl bug
>>   - 2 errors: changing file permissions
>>   - warning (do not add new typedefs): need rewrite too much code
>>   - warning: using volatile
>> These issues need TI guys to fix in the future. I also marked in the
>> commits
>> after I fixed the coding style.
>>
>> The following changes since commit
>> bb31cd255b992ee994b6a6aa328acede6460d747:
>>    Tim Gardner (1):
>>          UBUNTU: Ubuntu-2.6.34-902.6
>>
>> are available in the git repository at:
>>
>>    git://kernel.ubuntu.com/roc/ubuntu-maverick ti-omap4
>>
> 
> NAK - test build FTBS. See attached.
> 

I've tested to build the kernel via both cross compiler and sbuild from source
package. I wanna try schroot to build it on our build server but don't have the
right permission to do that.

Building package is fine and kernel works fine on my board. How can I reproduce
the failure in your log.txt?

> While you're at it:
> 
> grep omap log.txt |grep warning
> 
> Why are these compiles so noisy? If TI has any hope of upstreaming any
> of this code they have to start paying attention to code quality and
> style issues.
> 

That's quit annoying. I've already told TI guys to improve their code quality
and fix the style issues.

Nicolas, how do you think of that? We need more help from you guys. It will also
help TI to push code to upstream, I believe.

Thanks,

Please find my sbuild log in attachment file.
-Bryan
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: linux-ti-omap4_2.6.34-903.7+style0-armel-20100729-1516
URL: <https://lists.ubuntu.com/archives/kernel-team/attachments/20100729/8108a406/attachment.ksh>