lkml.org 
[lkml]   [2009]   [Mar]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [Tux3] Tux3 report: Tux3 Git tree available
Date
Nick Piggin <nickpiggin@yahoo.com.au> writes:

>> There are a couple of issues, one is u64 being (long) instead of
>> (long long) as you say, and the other is variable type sizes like
>> loff_t. That specific one isn't actually a problem, we can just refuse
>> to support 32 bit libc file ops, but there may be others. We had a
>> world of pain before (L) arrived, then with (L) it was easy. Maybe
>> just edit them all to (long long) for now, and damn the line length.
>
> Yes please do this. A significant style change like this that lots of
> code already does I think is best first discussed as a standalone
> change to kernel rather than everyone developing their own convention.

BTW, personally I wonder whether there are any suggestion - how early
stage do we try to start review process? Someone suggests it should be
early, but how early?

I know tux3 still have to work for various things, however, people join
to develop those, and see the progress? Or people just want to see the
result of various work later? ...
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>


\
 
 \ /
  Last update: 2009-03-12 18:05    [W:0.115 / U:0.908 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site