kernel.git/drivers/mtd/mtdconcat.c, branch linux-3.2.y

mtd: utilize `mtd_is_*()' functions

2011-09-21T06:19:06Z

Signed-off-by: Brian Norris Signed-off-by: Artem Bityutskiy

mtd: spelling fixes

2011-09-11T12:02:16Z

Signed-off-by: Brian Norris Signed-off-by: Artem Bityutskiy

mtd: mtdconcat: fix NAND OOB write

2011-05-25T00:54:50Z

Currently mtdconcat is broken for NAND. An attemtpt to create JFFS2 filesystem on concatenation of several NAND devices fails with OOB write errors. This patch fixes that problem. Signed-off-by: Felix Radensky Signed-off-by: Artem Bityutskiy Cc: stable@kernel.org Signed-off-by: David Woodhouse

mtd: adapt writebufsize calculation for concat

2011-03-11T14:22:42Z

If different chips with different writebufsize are concatenated, the writebufsize from the concat device has to be taken from the device with the largest writebuffer. This writebufsize is used later on in the UBI layer for the min I/O size. Signed-off-by: Holger Brunck Signed-off-by: Artem Bityutskiy Signed-off-by: David Woodhouse

mtd: initialize writebufsize in the MTD object of a partition

2011-01-06T15:35:58Z

Propagate the writebufsize to the partition's MTD object so that UBI can set correct value for it's minimal I/O size using the writebufsize field of MTD object of the partition. By previous patches we added proper writebufsize field initialization. Next patch can now change UBI to use this field for setting the minimal I/O size. Signed-off-by: Anatolij Gustschin Signed-off-by: Artem Bityutskiy Signed-off-by: David Woodhouse

mtd: Update copyright notices

2010-08-08T19:58:20Z

Signed-off-by: David Woodhouse

mtd: mtdconcat: fix bug with uninitialized lock and unlock functions

2010-08-02T08:04:20Z

Test if a lock or unlock function is present (pointer not NULL) before calling it, to prevent a kernel dump. Artem: removed extra blank lines Signed-off-by: Martin Krause Signed-off-by: Artem Bityutskiy Signed-off-by: David Woodhouse

drivers/mtd: Use kmemdup

2010-05-15T22:07:01Z

Use kmemdup when some other buffer is immediately copied into the allocated region. A simplified version of the semantic patch that makes this change is as follows: (http://coccinelle.lip6.fr/) // @@ expression from,to,size,flag; statement S; @@ - to = \(kmalloc\|kzalloc\)(size,flag); + to = kmemdup(from,size,flag); if (to==NULL || ...) S - memcpy(to, from, size); // Signed-off-by: Julia Lawall Signed-off-by: David Woodhouse

mtd: mtdconcat: prevent a read from eraseregions[-1]

2009-09-19T18:18:46Z

If the erase region was found in the first iteration we read from eraseregions[-1] Signed-off-by: Roel Kluin Signed-off-by: Andrew Morton Signed-off-by: David Woodhouse

NOMMU: Add support for direct mapping through mtdconcat if possible

2009-03-24T09:01:08Z

Add support for direct mapping through mtdconcat, if possible, by attaching the samebacking_dev_info structure to the master. It has some restrictions: (1) It won't permit direct mapping of concatenated devices that have differing BDIs. (2) It doesn't support maps that span the 'gap' between devices, although it possibly could if the devices spanned across return compatible (ie. contiguous) addresses from their get_unmapped_area() ops. Signed-off-by: Gavin Lambert Signed-off-by: David Howells Tested-by: Bernd Schmidt Signed-off-by: David Woodhouse