mtd: rawnand: Avoid indirect access to ->data_buf()

The logic in nand_do_read_ops() is to use a bufpoi variable, either
set to the original buffer, or set to a bounce buffer which in the end
happens to be chip->data_buf depending on the value of the
use_bounce_buf boolean. This is not a reason to call chip->data_buf
directly when we know that we are using the bounce buffer. Let's use
bufpoi instead to be consistent.

Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
Link: https://lore.kernel.org/linux-mtd/20200507105241.14299-7-miquel.raynal@bootlin.com

diff --git a/drivers/mtd/nand/raw/nand_base.c b/drivers/mtd/nand/raw/nand_base.c
index e2d96653fc3fd8fb22e8c8eb970eaf271d869a74..c440f11a34e9e467e6bec07c982f5671f8bdf5e0 100644 (file)
--- a/drivers/mtd/nand/raw/nand_base.c
+++ b/drivers/mtd/nand/raw/nand_base.c
@@ -3293,7 +3293,7 @@ read_retry:
                                        /* Invalidate page cache */
                                        chip->pagecache.page = -1;
                                }
-                               memcpy(buf, chip->data_buf + col, bytes);
+                               memcpy(buf, bufpoi + col, bytes);
                        }
 
                        if (unlikely(oob)) {