From: kernel test robot <lkp@intel.com>
To: Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>,
srini@kernel.org, linux-arm-msm@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, gregkh@linuxfoundation.org,
quic_bkumar@quicinc.com, linux-kernel@vger.kernel.org,
quic_chennak@quicinc.com, dri-devel@lists.freedesktop.org,
arnd@arndb.de, dmitry.baryshkov@oss.qualcomm.com
Subject: Re: [PATCH v2 1/2] misc: fastrpc: Refactor mmap and munmap logic into helper functions
Date: Sat, 29 Nov 2025 19:10:09 +0800 [thread overview]
Message-ID: <202511291834.zu81Ud77-lkp@intel.com> (raw)
In-Reply-To: <20251128103428.1119696-2-ekansh.gupta@oss.qualcomm.com>
Hi Ekansh,
kernel test robot noticed the following build warnings:
[auto build test WARNING on char-misc/char-misc-testing]
[also build test WARNING on char-misc/char-misc-next char-misc/char-misc-linus linus/master v6.18-rc7 next-20251128]
[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/Ekansh-Gupta/misc-fastrpc-Refactor-mmap-and-munmap-logic-into-helper-functions/20251128-183620
base: char-misc/char-misc-testing
patch link: https://lore.kernel.org/r/20251128103428.1119696-2-ekansh.gupta%40oss.qualcomm.com
patch subject: [PATCH v2 1/2] misc: fastrpc: Refactor mmap and munmap logic into helper functions
config: arm-allyesconfig (https://download.01.org/0day-ci/archive/20251129/202511291834.zu81Ud77-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251129/202511291834.zu81Ud77-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/202511291834.zu81Ud77-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/misc/fastrpc.c: In function 'fastrpc_req_munmap_dsp':
>> drivers/misc/fastrpc.c:1825:23: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
1825 | args[0].ptr = (u64) &req_msg;
| ^
drivers/misc/fastrpc.c: In function 'fastrpc_req_map_dsp':
drivers/misc/fastrpc.c:1897:23: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
1897 | args[0].ptr = (u64)&req_msg;
| ^
drivers/misc/fastrpc.c:1903:23: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
1903 | args[1].ptr = (u64)&pages;
| ^
drivers/misc/fastrpc.c:1906:23: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
1906 | args[2].ptr = (u64)&rsp_msg;
| ^
vim +1825 drivers/misc/fastrpc.c
1813
1814 static int fastrpc_req_munmap_dsp(struct fastrpc_user *fl, u64 raddr, u64 size)
1815 {
1816 struct fastrpc_invoke_args args[1] = { [0] = { 0 } };
1817 struct fastrpc_munmap_req_msg req_msg;
1818 int err;
1819 u32 sc;
1820
1821 req_msg.client_id = fl->client_id;
1822 req_msg.size = size;
1823 req_msg.vaddr = raddr;
1824
> 1825 args[0].ptr = (u64) &req_msg;
1826 args[0].length = sizeof(req_msg);
1827
1828 sc = FASTRPC_SCALARS(FASTRPC_RMID_INIT_MUNMAP, 1, 0);
1829 err = fastrpc_internal_invoke(fl, true, FASTRPC_INIT_HANDLE, sc,
1830 &args[0]);
1831
1832 return err;
1833 }
1834
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-11-29 11:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 10:34 [PATCH v2 0/2] misc: fastrpc: Refactor and add userspace buffer support Ekansh Gupta
2025-11-28 10:34 ` [PATCH v2 1/2] misc: fastrpc: Refactor mmap and munmap logic into helper functions Ekansh Gupta
2025-11-29 11:10 ` kernel test robot [this message]
2025-11-28 10:34 ` [PATCH v2 2/2] misc: fastrpc: Support mapping userspace-allocated buffers Ekansh Gupta
2025-11-28 15:32 ` Greg KH
2025-12-02 6:07 ` Ekansh Gupta
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=202511291834.zu81Ud77-lkp@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ekansh.gupta@oss.qualcomm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=quic_bkumar@quicinc.com \
--cc=quic_chennak@quicinc.com \
--cc=srini@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox