summaryrefslogtreecommitdiff
path: root/Documentation/devicetree/bindings/mtd
diff options
context:
space:
mode:
authorMiquel Raynal <miquel.raynal@free-electrons.com>2018-01-12 10:13:36 +0100
committerBoris Brezillon <boris.brezillon@free-electrons.com>2018-01-12 10:30:48 +0100
commit87e89ce8d0d14f573c068c61bec2117751fb5103 (patch)
treeb3a8854bf8bd9ae415dec53219c00852998641c6 /Documentation/devicetree/bindings/mtd
parent12663b442e5ac5aa3d6097cd3f287c71ba46d26e (diff)
mtd: nand: Fix nand_do_read_oob() return value
Starting from commit 041e4575f034 ("mtd: nand: handle ECC errors in OOB"), nand_do_read_oob() (from the NAND core) did return 0 or a negative error, and the MTD layer expected it. However, the trend for the NAND layer is now to return an error or a positive number of bitflips. Deciding which status to return to the user belongs to the MTD layer. Commit e47f68587b82 ("mtd: check for max_bitflips in mtd_read_oob()") brought this logic to the mtd_read_oob() function while the return value coming from nand_do_read_oob() (called by the ->_read_oob() hook) was left unchanged. Fixes: e47f68587b82 ("mtd: check for max_bitflips in mtd_read_oob()") Cc: stable@vger.kernel.org Signed-off-by: Miquel Raynal <miquel.raynal@free-electrons.com> Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
Diffstat (limited to 'Documentation/devicetree/bindings/mtd')
0 files changed, 0 insertions, 0 deletions