From: Thomas Gleixner <tglx@linutronix.de>
To: linux-mtd@lists.infradead.org
Subject: MTD git repository status
Date: Mon, 7 Nov 2005 19:15:03 +0100 [thread overview]
Message-ID: <200511071915.03263.tglx@linutronix.de> (raw)
Hi folks,
I've updated the mtd git repository hopefully in time for 2.6.15.
http://www.kernel.org/git/?p=linux/kernel/git/tglx/mtd-2.6.git;a=summary
tglx
Following changes are not included into the update:
- [JFFS2] Erase Block Header(EBH)
Needs proper testing and stabilizing first
- [MTD] NAND: OOB changes
Needs more thoughts. I'm particularly unhappy with the introduction of new
functions and the still pending problem of the automatic placement/retrieval
of oob data. The change should subsume and/or extend the oob_info
functionality rather than introducing a parallel solution.
- [MTD] NAND: nandsim
There is still the big Kconfig clutter. For testing environments it _is_
sufficient to provide all this information as module parameters. No need to
bloat the config file
- [MTD] ONENAND: Simulator
Is depending on arch/??? probably ARM and uses some obscure __iomem*
constructs.
Can the authors please shed some light on the status of following drivers:
- [MTD] maps mphysram.c
It needs a bunch of coding style cleanups.
- [MTD] devices ramtd.c
Needs probably a go on the fixed size allocation already marked with
/* FIXME */
- [MTD] ssfdc.c
AFAIK the driver is mostly functional. What's missing ?
It needs a bunch of coding style cleanups.
next reply other threads:[~2005-11-07 18:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 18:15 Thomas Gleixner [this message]
2005-11-07 19:24 ` MTD git repository status Thomas Gleixner
2005-11-07 19:26 ` Charles Manning
2005-11-11 6:57 ` Vitaly Wool
2005-11-07 20:43 ` Vitaly Wool
2005-11-07 21:33 ` MTD git repository status ==> oob_info & other methods Charles Manning
2005-11-08 14:10 ` MTD git repository status Artem B. Bityutskiy
2005-11-08 20:03 ` Charles Manning
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=200511071915.03263.tglx@linutronix.de \
--to=tglx@linutronix.de \
--cc=linux-mtd@lists.infradead.org \
/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