diff options
| author | Miquel Raynal <miquel.raynal@bootlin.com> | 2020-05-07 12:52:34 +0200 |
|---|---|---|
| committer | Miquel Raynal <miquel.raynal@bootlin.com> | 2020-05-11 09:51:42 +0200 |
| commit | 21b5cf3f6467cf608756151066941792f340c986 (patch) | |
| tree | bf907a5b116428540a027b21a1ca0f6ab9a54ca2 /tools/perf/scripts/python/bin | |
| parent | mtd: rawnand: Rename the use_bufpoi variables (diff) | |
| download | linux-21b5cf3f6467cf608756151066941792f340c986.tar.gz linux-21b5cf3f6467cf608756151066941792f340c986.zip | |
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
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions