From: kernel test robot <lkp@intel.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: kbuild-all@lists.01.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [staging:staging-testing 227/311] drivers/staging/r8188eu/hal/rtl8188e_hal_init.c:366:3: error: implicit declaration of function 'vfree'; did you mean 'kvfree'?
Date: Wed, 11 Aug 2021 11:35:09 +0800 [thread overview]
Message-ID: <202108111100.qsE6PB8I-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2852 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git staging-testing
head: ae7471cae00a432d1c9692452b1b9175a8f3c1b3
commit: 71f09c5ae9d2c2c1344987b104dc167ab1922b72 [227/311] staging: r8188eu: Remove wrapper around vfree
config: mips-allyesconfig (attached as .config)
compiler: mips-linux-gcc (GCC) 10.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/commit/?id=71f09c5ae9d2c2c1344987b104dc167ab1922b72
git remote add staging https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
git fetch --no-tags staging staging-testing
git checkout 71f09c5ae9d2c2c1344987b104dc167ab1922b72
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 make.cross ARCH=mips
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/staging/r8188eu/hal/rtl8188e_hal_init.c: In function 'rtw_IOL_cmd_tx_pkt_buf_dump':
>> drivers/staging/r8188eu/hal/rtl8188e_hal_init.c:366:3: error: implicit declaration of function 'vfree'; did you mean 'kvfree'? [-Werror=implicit-function-declaration]
366 | vfree(pbuf);
| ^~~~~
| kvfree
cc1: some warnings being treated as errors
vim +366 drivers/staging/r8188eu/hal/rtl8188e_hal_init.c
338
339 void rtw_IOL_cmd_tx_pkt_buf_dump(struct adapter *Adapter, int data_len)
340 {
341 u32 fifo_data, reg_140;
342 u32 addr, rstatus, loop = 0;
343 u16 data_cnts = (data_len/8)+1;
344 u8 *pbuf = rtw_zvmalloc(data_len+10);
345 DBG_88E("###### %s ######\n", __func__);
346
347 rtw_write8(Adapter, REG_PKT_BUFF_ACCESS_CTRL, TXPKT_BUF_SELECT);
348 if (pbuf) {
349 for (addr = 0; addr < data_cnts; addr++) {
350 rtw_write32(Adapter, 0x140, addr);
351 rtw_usleep_os(2);
352 loop = 0;
353 do {
354 rstatus = (reg_140 = rtw_read32(Adapter, REG_PKTBUF_DBG_CTRL)&BIT24);
355 if (rstatus) {
356 fifo_data = rtw_read32(Adapter, REG_PKTBUF_DBG_DATA_L);
357 memcpy(pbuf+(addr*8), &fifo_data, 4);
358
359 fifo_data = rtw_read32(Adapter, REG_PKTBUF_DBG_DATA_H);
360 memcpy(pbuf+(addr*8+4), &fifo_data, 4);
361 }
362 rtw_usleep_os(2);
363 } while (!rstatus && (loop++ < 10));
364 }
365 rtw_IOL_cmd_buf_dump(Adapter, data_len, pbuf);
> 366 vfree(pbuf);
367 }
368 DBG_88E("###### %s ######\n", __func__);
369 }
370
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 70960 bytes --]
reply other threads:[~2021-08-11 3:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202108111100.qsE6PB8I-lkp@intel.com \
--to=lkp@intel.com \
--cc=Larry.Finger@lwfinger.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.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