From: Wookey <wookey@wookware.org>
To: linux-embedded@vger.kernel.org
Cc: Charles Manning <manningc2@actrix.gen.nz>
Subject: YAFFS mainlining process currently underway
Date: Mon, 15 Nov 2010 11:35:11 +0000 [thread overview]
Message-ID: <20101115113511.GL28472@dream.aleph1.co.uk> (raw)
Thanks to a kick (and some money to enable the necessary concentration
on the job) from CELF/Google a YAFFS git branch intended for mainline
merging has been created.
Initial patches are currently under discussion on the fsdevel list. I
thought it worth mentioning here as this is a subject largely of
interrest to embedded people.
http://www.spinics.net/lists/linux-fsdevel/threads.html#39158
http://www.spinics.net/lists/linux-fsdevel/msg39142.html
Do please comment.
The main constraint to bear in mind, is the need to keep the
in-linux branch compatible with the yaffs.net 'works with all OSes,
not just Linux (and old kernel versions too)' branch. So that means
compilers other than GCC, function veneers to interface with the
various OS-provided filesystem and hardware access functions, the
built-in trace system. Some of this is stuff that would go away or use
built-in linux functionality with a linux-only filesystem, but this
isn't a linux-only filesystem, so some compromise is needed.
The discussion seems to be going well so far.
The codebase has been changed to Linux coding style and had a lot of
cruft removed:
* Multi-OS code has been removed.
* Types changed from __u32-->u32 etc.
* typedefs removed.
* Lindenting done.
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
reply other threads:[~2010-11-15 11:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101115113511.GL28472@dream.aleph1.co.uk \
--to=wookey@wookware.org \
--cc=linux-embedded@vger.kernel.org \
--cc=manningc2@actrix.gen.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox