From: kernel test robot <lkp@intel.com>
To: Cristian Marussi <cristian.marussi@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, arm-scmi@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, sudeep.holla@arm.com,
james.quinlan@broadcom.com, f.fainelli@gmail.com,
vincent.guittot@linaro.org, etienne.carriere@foss.st.com,
peng.fan@oss.nxp.com, michal.simek@amd.com,
quic_sibis@quicinc.com, quic_nkela@quicinc.com, ptosi@google.com,
dan.carpenter@linaro.org, souvik.chakravarty@arm.com,
Peng Fan <peng.fan@nxp.com>,
Cristian Marussi <cristian.marussi@arm.com>
Subject: Re: [PATCH 1/8] firmware: arm_scmi: Introduce setup_shmem_iomap
Date: Mon, 8 Jul 2024 10:19:35 +0800 [thread overview]
Message-ID: <202407080937.AYEaDXCD-lkp@intel.com> (raw)
In-Reply-To: <20240707002055.1835121-2-cristian.marussi@arm.com>
Hi Cristian,
kernel test robot noticed the following build warnings:
[auto build test WARNING on soc/for-next]
[also build test WARNING on next-20240703]
[cannot apply to linus/master v6.10-rc7]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Cristian-Marussi/firmware-arm_scmi-Introduce-setup_shmem_iomap/20240707-082513
base: https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git for-next
patch link: https://lore.kernel.org/r/20240707002055.1835121-2-cristian.marussi%40arm.com
patch subject: [PATCH 1/8] firmware: arm_scmi: Introduce setup_shmem_iomap
config: arm-randconfig-r111-20240708 (https://download.01.org/0day-ci/archive/20240708/202407080937.AYEaDXCD-lkp@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project a0c6b8aef853eedaa0980f07c0a502a5a8a9740e)
reproduce: (https://download.01.org/0day-ci/archive/20240708/202407080937.AYEaDXCD-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202407080937.AYEaDXCD-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/firmware/arm_scmi/shmem.c:170:16: sparse: sparse: incorrect type in return expression (different address spaces) @@ expected void * @@ got void [noderef] __iomem *[assigned] addr @@
drivers/firmware/arm_scmi/shmem.c:170:16: sparse: expected void *
drivers/firmware/arm_scmi/shmem.c:170:16: sparse: got void [noderef] __iomem *[assigned] addr
drivers/firmware/arm_scmi/shmem.c:139:6: sparse: sparse: symbol 'setup_shmem_iomap' redeclared with different type (different address spaces):
drivers/firmware/arm_scmi/shmem.c:139:6: sparse: void *extern [addressable] [noderef] [toplevel] __iomem setup_shmem_iomap( ... )
drivers/firmware/arm_scmi/shmem.c: note: in included file:
drivers/firmware/arm_scmi/common.h:330:14: sparse: note: previously declared as:
drivers/firmware/arm_scmi/common.h:330:14: sparse: void [noderef] __iomem *extern [addressable] [toplevel] setup_shmem_iomap( ... )
vim +170 drivers/firmware/arm_scmi/shmem.c
138
139 void *__iomem
140 setup_shmem_iomap(struct scmi_chan_info *cinfo, struct device *dev, bool tx)
141 {
142 const char *desc = tx ? "Tx" : "Rx";
143 int ret, idx = tx ? 0 : 1;
144 struct device *cdev = cinfo->dev;
145 struct device_node *shmem;
146 resource_size_t size;
147 struct resource res;
148 void __iomem *addr;
149
150 shmem = of_parse_phandle(cdev->of_node, "shmem", idx);
151 if (!of_device_is_compatible(shmem, "arm,scmi-shmem")) {
152 of_node_put(shmem);
153 return ERR_PTR(-ENXIO);
154 }
155
156 ret = of_address_to_resource(shmem, 0, &res);
157 of_node_put(shmem);
158 if (ret) {
159 dev_err(cdev, "failed to get SCMI %s shared memory\n", desc);
160 return ERR_PTR(ret);
161 }
162
163 size = resource_size(&res);
164 addr = devm_ioremap(dev, res.start, size);
165 if (!addr) {
166 dev_err(dev, "failed to ioremap SCMI %s shared memory\n", desc);
167 return ERR_PTR(-EADDRNOTAVAIL);
168 }
169
> 170 return addr;
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-07-08 2:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-07 0:20 [PATCH 0/8] Make SCMI transport as standalone drivers Cristian Marussi
2024-07-07 0:20 ` [PATCH 1/8] firmware: arm_scmi: Introduce setup_shmem_iomap Cristian Marussi
2024-07-07 16:48 ` Nikunj Kela
2024-07-08 9:26 ` Cristian Marussi
2024-07-08 2:19 ` kernel test robot [this message]
2024-07-07 0:20 ` [PATCH 2/8] firmware: arm_scmi: Introduce packet handling helpers Cristian Marussi
2024-07-08 3:59 ` kernel test robot
2024-07-07 0:20 ` [PATCH 3/8] firmware: arm_scmi: Add support for standalone transport drivers Cristian Marussi
2024-07-07 0:20 ` [PATCH 4/8] firmware: arm_scmi: Make MBOX transport a standalone driver Cristian Marussi
2024-07-07 0:20 ` [PATCH 5/8] firmware: arm_scmi: Make SMC " Cristian Marussi
2024-07-07 16:03 ` kernel test robot
2024-07-07 16:52 ` Nikunj Kela
2024-07-08 14:27 ` Cristian Marussi
2024-07-08 15:23 ` Nikunj Kela
2024-07-08 15:47 ` Cristian Marussi
2024-07-08 17:59 ` Nikunj Kela
2024-07-09 10:33 ` Cristian Marussi
2024-10-15 16:31 ` Cristian Marussi
2024-07-09 12:45 ` kernel test robot
2024-07-10 3:37 ` kernel test robot
2024-07-07 0:20 ` [PATCH 6/8] firmware: arm_scmi: Make OPTEE " Cristian Marussi
2024-07-09 2:21 ` Dan Carpenter
2024-07-09 9:55 ` Cristian Marussi
2024-07-07 0:20 ` [PATCH 7/8] firmware: arm_scmi: Make VirtIO " Cristian Marussi
2024-07-08 5:53 ` kernel test robot
2024-07-07 0:20 ` [PATCH 8/8] firmware: arm_scmi: Remove legacy transport-layer code Cristian Marussi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202407080937.AYEaDXCD-lkp@intel.com \
--to=lkp@intel.com \
--cc=arm-scmi@vger.kernel.org \
--cc=cristian.marussi@arm.com \
--cc=dan.carpenter@linaro.org \
--cc=etienne.carriere@foss.st.com \
--cc=f.fainelli@gmail.com \
--cc=james.quinlan@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=ptosi@google.com \
--cc=quic_nkela@quicinc.com \
--cc=quic_sibis@quicinc.com \
--cc=souvik.chakravarty@arm.com \
--cc=sudeep.holla@arm.com \
--cc=vincent.guittot@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.