Message	SHA1
[MTD] Fix fwh_lock locking ... This is on a custom board with a mapping driver access to an ST M50LPW080 chip. This chip is probed successfully with do_map_probe("jedec_probe",...). If I use the mtdchar interface to perform unlock->erase->program->lock on any of the 16 eraseblocks in the chip, the chip is left in FL_STATUS mode while the data structures believe that the chip is in FL_READY mode. Hence, any subsequent reads to any flash byte results in 0x80 being read. Signed-off-by: Shashi Rao <shashi@sun.com> Signed-off-by: David Woodhouse <dwmw2@infradead.org> Shashi Rao   authored and   David Woodhouse   commited 2007-04-17 14:11:20 -04:00	e6be133b68
[MTD] chips: Clean up trailing white spaces ... Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Thomas Gleixner   commited 2005-11-07 14:45:15 +01:00	1f948b43f7
[MTD] XIP for AMD CFI flash. ... Author: Vitaly Wool <vwool@ru.mvista.com> Signed-off-by: Todd Poynor <tpoynor@mvista.com> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Todd Poynor   authored and   Thomas Gleixner   commited 2005-06-29 14:18:40 +02:00	02b15e343a
Linux-2.6.12-rc2 ... Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip! Linus Torvalds   commited 2005-04-16 15:20:36 -07:00	1da177e4c3