All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [linux-review:UPDATE-20201101-053738/Anant-Thazhemadam/net-usb-usbnet-update-__usbnet_-read-write-_cmd-to-use-new-API/20201010-145950 1/1] drivers/net/usb/usbnet.c:1990:9: error: implicit declaration of function 'usb_control_msg_recv'; did you mean
Date: Fri, 13 Nov 2020 15:31:00 +0800	[thread overview]
Message-ID: <202011131557.IbvOQuhs-lkp@intel.com> (raw)

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

tree:   https://github.com/0day-ci/linux/commits/UPDATE-20201101-053738/Anant-Thazhemadam/net-usb-usbnet-update-__usbnet_-read-write-_cmd-to-use-new-API/20201010-145950
head:   d295ce2cdd3fbf4f9951db971c27ea4f19bc6cb1
commit: d295ce2cdd3fbf4f9951db971c27ea4f19bc6cb1 [1/1] net: usb: usbnet: update __usbnet_{read|write}_cmd() to use new API
config: xtensa-allyesconfig (attached as .config)
compiler: xtensa-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://github.com/0day-ci/linux/commit/d295ce2cdd3fbf4f9951db971c27ea4f19bc6cb1
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review UPDATE-20201101-053738/Anant-Thazhemadam/net-usb-usbnet-update-__usbnet_-read-write-_cmd-to-use-new-API/20201010-145950
        git checkout d295ce2cdd3fbf4f9951db971c27ea4f19bc6cb1
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=xtensa 

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/usb/usbnet.c: In function '__usbnet_read_cmd':
>> drivers/net/usb/usbnet.c:1990:9: error: implicit declaration of function 'usb_control_msg_recv'; did you mean 'usb_control_msg'? [-Werror=implicit-function-declaration]
    1990 |  return usb_control_msg_recv(dev->udev, 0,
         |         ^~~~~~~~~~~~~~~~~~~~
         |         usb_control_msg
   drivers/net/usb/usbnet.c: In function '__usbnet_write_cmd':
>> drivers/net/usb/usbnet.c:2008:9: error: implicit declaration of function 'usb_control_msg_send'; did you mean 'usb_control_msg'? [-Werror=implicit-function-declaration]
    2008 |  return usb_control_msg_send(dev->udev, 0,
         |         ^~~~~~~~~~~~~~~~~~~~
         |         usb_control_msg
   cc1: some warnings being treated as errors

vim +1990 drivers/net/usb/usbnet.c

  1985	
  1986		netdev_dbg(dev->net, "usbnet_read_cmd cmd=0x%02x reqtype=%02x"
  1987			   " value=0x%04x index=0x%04x size=%d\n",
  1988			   cmd, reqtype, value, index, size);
  1989	
> 1990		return usb_control_msg_recv(dev->udev, 0,
  1991					    cmd, reqtype, value, index, data, size,
  1992					    USB_CTRL_GET_TIMEOUT, GFP_KERNEL);
  1993	}
  1994	
  1995	static int __usbnet_write_cmd(struct usbnet *dev, u8 cmd, u8 reqtype,
  1996				      u16 value, u16 index, const void *data,
  1997				      u16 size)
  1998	{
  1999		netdev_dbg(dev->net, "usbnet_write_cmd cmd=0x%02x reqtype=%02x"
  2000			   " value=0x%04x index=0x%04x size=%d\n",
  2001			   cmd, reqtype, value, index, size);
  2002	
  2003		if (size && !data) {
  2004			WARN_ON_ONCE(1);
  2005			return -EINVAL;
  2006		}
  2007	
> 2008		return usb_control_msg_send(dev->udev, 0,
  2009					    cmd, reqtype, value, index, data, size,
  2010					    USB_CTRL_SET_TIMEOUT, GFP_KERNEL);
  2011	}
  2012	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 65044 bytes --]

                 reply	other threads:[~2020-11-13  7:31 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=202011131557.IbvOQuhs-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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.