linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Srinivasan Raju <srini.raju@purelifi.com>
Cc: kbuild-all@lists.01.org, Kalle Valo <kvalo@codeaurora.org>,
	linux-wireless@vger.kernel.org
Subject: [wireless-drivers-next:pending 1/2] drivers/net/wireless/purelifi/plfxlc/usb.c:962:20: error: 'suspend' undeclared here (not in a function)
Date: Thu, 4 Mar 2021 15:09:21 +0800	[thread overview]
Message-ID: <202103041519.sFFTWPMg-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2459 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.git pending
head:   6a50a3c949db01857a1165ba677d092a9f24fd1f
commit: b8a12d2aca7ce360b32b616844bc1561fce37333 [1/2] wireless: Initial driver submission for pureLiFi STA devices
config: parisc-allyesconfig (attached as .config)
compiler: hppa-linux-gcc (GCC) 9.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/kvalo/wireless-drivers-next.git/commit/?id=b8a12d2aca7ce360b32b616844bc1561fce37333
        git remote add wireless-drivers-next https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.git
        git fetch --no-tags wireless-drivers-next pending
        git checkout b8a12d2aca7ce360b32b616844bc1561fce37333
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=parisc 

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/net/wireless/purelifi/plfxlc/usb.c:962:20: error: 'suspend' undeclared here (not in a function)
     962 |  .suspend        = suspend,
         |                    ^~~~~~~
>> drivers/net/wireless/purelifi/plfxlc/usb.c:963:20: error: 'resume' undeclared here (not in a function); did you mean 'resource'?
     963 |  .resume         = resume,
         |                    ^~~~~~
         |                    resource
   drivers/net/wireless/purelifi/plfxlc/usb.c:909:29: warning: 'get_purelifi_usb' defined but not used [-Wunused-function]
     909 | static struct purelifi_usb *get_purelifi_usb(struct usb_interface *intf)
         |                             ^~~~~~~~~~~~~~~~


vim +/suspend +962 drivers/net/wireless/purelifi/plfxlc/usb.c

   954	
   955	static struct usb_driver driver = {
   956		.name        = KBUILD_MODNAME,
   957		.id_table    = usb_ids,
   958		.probe        = probe,
   959		.disconnect    = disconnect,
   960		.pre_reset    = pre_reset,
   961		.post_reset    = post_reset,
 > 962		.suspend        = suspend,
 > 963		.resume         = resume,
   964		.disable_hub_initiated_lpm = 1,
   965	};
   966	

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

                 reply	other threads:[~2021-03-04  7:12 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=202103041519.sFFTWPMg-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=srini.raju@purelifi.com \
    /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;
as well as URLs for NNTP newsgroup(s).