[PATCH] small fix for drivers/mtd/chips/map_ram.c in 2.4

[Ian Campbell <icampbell@arcomcontrols.com>]

[-- Attachment #1: Type: text/plain, Size: 879 bytes --]

Hi, 

The attached one-liner was necessary to allow me to mount a JFFS2 file
system using an MTD device based on the map_ram map driver. 

It sets the state to MTD_ERASE_DONE in mapram_erase, if memory serves (I
did it a couple of weeks ago) not having this was causing badness in
jffs2_erase_callback.

Cheers,
Ian.
-- 
Ian Campbell
Design Engineer

Arcom Control Systems Ltd,
Clifton Road,
Cambridge CB1 7EA
United Kingdom

Tel: +44 (0)1223 403465
E-Mail: icampbell@arcomcontrols.com
Web: http://www.arcomcontrols.com


________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com
________________________________________________________________________

[-- Attachment #2: mtd.map_ram.patch --]
[-- Type: text/plain, Size: 289 bytes --]

--- kernel-2.4.18.orig/drivers/mtd/chips/map_ram.c
+++ kernel-2.4.18/drivers/mtd/chips/map_ram.c
@@ -107,5 +107,7 @@
 	for (i=0; i<instr->len; i++)
 		map->write8(map, 0xFF, instr->addr + i);
 
+	instr->state = MTD_ERASE_DONE;
+
 	if (instr->callback)
 		instr->callback(instr);