Re: [Yaffs] Offers for help on yaffs

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: Luc Van Oostenryck
Date:  
To: Charles Manning
CC: yaffs
Subject: Re: [Yaffs] Offers for help on yaffs
Charles Manning wrote:
> Hi folks
>
> ...
>
> 1) I keep my primary focus on the yaffs_guts stuff, as well as supporting
> yaffs Direct etc.
>
> 2) Someone take ownership of the Linux-specific stuff for 2.6 and the YAFFS2
> codebase, including handling incoming patches etc as well as interaction with
> the kernel community. This would be the prime focus of the Linux effort.
>
> 3) Any other Linux uses like 2.4 compatability or maintenance of the YAFFS1
> codebase might need someone else to do the work.
>
> I would like volunteers for someone to do job (2). This need not be forever.
> A 6 month or so tour of duty would be fine, IMHO, as would two or three
> people sharing the task, but preferably we can end up with a situation where
> more people get actively involved in the support and improvement of YAFFS to
> everyone's advantage.
>



Hi Charles,


I can count on me for helping to include yaffs into the main Linux tree.
But I have a few question:
- What do you mean exactly by "take ownership of the ..."?
Having CVS commit access to the yaffs CVS repository or do you mean to
maintain a separate tree/patchset directly oriented for inclusion into the kernel tree?

- From my understanding, I don't think that with the current Linux kernel development line
there will be big problems for the Linux comunity to accept the inclusion of yaffs into
the main kernel tree (when ready first propose to Andrew Morton for inclusion into the -mm tree,
inclusion into the main tree will follow) except that the current yaffs code,
especially yaffs_guts, is far from respecting the Linux Coding Style
(indentation, #ifdef __KERNEL__/WINCE/...).
Is this a problem?



Luc Van Oostenryck