[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20211117033220.2526552-1-peng.fan@oss.nxp.com>
Date: Wed, 17 Nov 2021 11:32:20 +0800
From: "Peng Fan (OSS)" <peng.fan@....nxp.com>
To: ohad@...ery.com, bjorn.andersson@...aro.org,
mathieu.poirier@...aro.org, o.rempel@...gutronix.de
Cc: shawnguo@...nel.org, s.hauer@...gutronix.de, kernel@...gutronix.de,
festevam@...il.com, linux-imx@....com,
linux-remoteproc@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Peng Fan <peng.fan@....com>, kernel test robot <lkp@...el.com>
Subject: [PATCH V2] remoteproc: coredump: correct argument 2 type for memcpy_fromio
From: Peng Fan <peng.fan@....com>
Address the sparse check warning:
>> drivers/remoteproc/remoteproc_coredump.c:169:53:
sparse: warning: incorrect type in argument 2 (different address spaces)
sparse: expected void const volatile [noderef] __iomem *src
sparse: got void *[assigned] ptr
Reported-by: kernel test robot <lkp@...el.com>
Signed-off-by: Peng Fan <peng.fan@....com>
---
V2:
Per Mathieu's comments, use 'const void __iomem *'
drivers/remoteproc/remoteproc_coredump.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/remoteproc/remoteproc_coredump.c b/drivers/remoteproc/remoteproc_coredump.c
index c892f433a323..37d86043ce5e 100644
--- a/drivers/remoteproc/remoteproc_coredump.c
+++ b/drivers/remoteproc/remoteproc_coredump.c
@@ -166,7 +166,7 @@ static void rproc_copy_segment(struct rproc *rproc, void *dest,
memset(dest, 0xff, size);
} else {
if (is_iomem)
- memcpy_fromio(dest, ptr, size);
+ memcpy_fromio(dest, (const void __iomem *)ptr, size);
else
memcpy(dest, ptr, size);
}
--
2.25.1
Powered by blists - more mailing lists