| commit | 89a82280a8e632b7a5b0ce70dd5bccfa2d3bc2c5 | |
| author | Nicolas Kaiser <nikai@nikai.net> | |
| Fri, 22 Oct 2010 10:47:24 +0000 (22 12:47 +0200) | ||
| committer | David Woodhouse <David.Woodhouse@intel.com> | |
| Tue, 26 Oct 2010 09:58:00 +0000 (26 10:58 +0100) | ||
| tree | edf833a4eca968961cca4d3612e6b405b9bcf73f | treesnapshot (tar.gz zip) |
| parent | 0b824d2b10eacd496c608a7c41a046862d48563b | commitdiff |
block2mtd: dubious assignment
When block2mtd_erase fails, a duplicated assignment instantly
changes instr->state from MTD_ERASE_FAILED to MTD_ERASE_DONE.
It looks to me like this might not be intended, or is it?
Signed-off-by: Nicolas Kaiser <nikai@nikai.net>
Acked-By: Joern Engel <joern@logfs.org>
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
When block2mtd_erase fails, a duplicated assignment instantly
changes instr->state from MTD_ERASE_FAILED to MTD_ERASE_DONE.
It looks to me like this might not be intended, or is it?
Signed-off-by: Nicolas Kaiser <nikai@nikai.net>
Acked-By: Joern Engel <joern@logfs.org>
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
| drivers/mtd/devices/block2mtd.c | diffblobblamehistory |