public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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/core/rtw_mlme.c:132:3: error: implicit declaration of function 'vfree'; did you mean 'kvfree'?
Date: Wed, 11 Aug 2021 11:29:01 +0800	[thread overview]
Message-ID: <202108111156.ww7dgBKu-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 4475 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-allmodconfig (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/core/rtw_mlme.c: In function '_rtw_free_mlme_priv':
>> drivers/staging/r8188eu/core/rtw_mlme.c:132:3: error: implicit declaration of function 'vfree'; did you mean 'kvfree'? [-Werror=implicit-function-declaration]
     132 |   vfree(pmlmepriv->free_bss_buf);
         |   ^~~~~
         |   kvfree
   cc1: some warnings being treated as errors
--
   drivers/staging/r8188eu/core/rtw_mp.c: In function '_rtw_mp_xmit_priv':
>> drivers/staging/r8188eu/core/rtw_mp.c:925:2: error: implicit declaration of function 'vfree'; did you mean 'kvfree'? [-Werror=implicit-function-declaration]
     925 |  vfree(pxmitpriv->pallocated_xmit_extbuf);
         |  ^~~~~
         |  kvfree
   cc1: some warnings being treated as errors
--
   drivers/staging/r8188eu/core/rtw_recv.c: In function '_rtw_free_recv_priv':
>> drivers/staging/r8188eu/core/rtw_recv.c:118:2: error: implicit declaration of function 'vfree'; did you mean 'kvfree'? [-Werror=implicit-function-declaration]
     118 |  vfree(precvpriv->pallocated_frame_buf);
         |  ^~~~~
         |  kvfree
   cc1: some warnings being treated as errors
--
   drivers/staging/r8188eu/core/rtw_sta_mgt.c: In function '_rtw_free_sta_priv':
>> drivers/staging/r8188eu/core/rtw_sta_mgt.c:214:4: error: implicit declaration of function 'vfree'; did you mean 'kvfree'? [-Werror=implicit-function-declaration]
     214 |    vfree(pstapriv->pallocated_stainfo_buf);
         |    ^~~~~
         |    kvfree
   cc1: some warnings being treated as errors
--
   drivers/staging/r8188eu/core/rtw_xmit.c: In function '_rtw_free_xmit_priv':
>> drivers/staging/r8188eu/core/rtw_xmit.c:255:2: error: implicit declaration of function 'vfree'; did you mean 'kvfree'? [-Werror=implicit-function-declaration]
     255 |  vfree(pxmitpriv->pallocated_frame_buf);
         |  ^~~~~
         |  kvfree
   cc1: some warnings being treated as errors
--
   drivers/staging/r8188eu/hal/odm_interface.c: In function 'ODM_FreeMemory':
>> drivers/staging/r8188eu/hal/odm_interface.c:88:2: error: implicit declaration of function 'vfree'; did you mean 'kvfree'? [-Werror=implicit-function-declaration]
      88 |  vfree(pPtr);
         |  ^~~~~
         |  kvfree
   cc1: some warnings being treated as errors
--
   drivers/staging/r8188eu/os_dep/ioctl_linux.c: In function 'rtw_wx_set_priv':
>> drivers/staging/r8188eu/os_dep/ioctl_linux.c:5578:3: error: implicit declaration of function 'vfree'; did you mean 'kvfree'? [-Werror=implicit-function-declaration]
    5578 |   vfree(ext);
         |   ^~~~~
         |   kvfree
   cc1: some warnings being treated as errors
--
   drivers/staging/r8188eu/os_dep/usb_intf.c: In function 'rtw_usb_if1_init':
>> drivers/staging/r8188eu/os_dep/usb_intf.c:705:4: error: implicit declaration of function 'vfree'; did you mean 'kvfree'? [-Werror=implicit-function-declaration]
     705 |    vfree(padapter);
         |    ^~~~~
         |    kvfree
   cc1: some warnings being treated as errors


vim +132 drivers/staging/r8188eu/core/rtw_mlme.c

   126	
   127		rtw_free_mlme_priv_ie_data(pmlmepriv);
   128	
   129		if (pmlmepriv) {
   130			rtw_mfree_mlme_priv_lock (pmlmepriv);
   131	
 > 132			vfree(pmlmepriv->free_bss_buf);
   133		}
   134	

---
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: 70809 bytes --]

                 reply	other threads:[~2021-08-11  3:29 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=202108111156.ww7dgBKu-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