From: kbuild test robot <lkp@intel.com>
To: Changming <charley.ashbringer@gmail.com>, gregkh@linuxfoundation.org
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
linux-usb@vger.kernel.org, thomas@winischhofer.net,
Changming Liu <liu.changm@northeastern.edu>
Subject: Re: [PATCH 5/6] USB: sisusbvga: change sisusb_read_mem_bulk
Date: Mon, 1 Jun 2020 06:43:18 +0800 [thread overview]
Message-ID: <202006010620.mYwc56Q1%lkp@intel.com> (raw)
In-Reply-To: <20200530014820.9967-6-liu.changm@northeastern.edu>
[-- Attachment #1: Type: text/plain, Size: 3913 bytes --]
Hi Changming,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on usb/usb-testing]
[also build test ERROR on balbi-usb/testing/next v5.7-rc7 next-20200529]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Changming/USB-sisusbvga-series-of-changes-char-to-u8/20200601-012438
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
config: x86_64-allyesconfig (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 2388a096e7865c043e83ece4e26654bd3d1a20d5)
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
# install x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>, old ones prefixed by <<):
>> drivers/usb/misc/sisusbvga/sisusb.c:2996:11: error: incompatible function pointer types initializing 'ssize_t (*)(struct file *, char *, size_t, loff_t *)' (aka 'long (*)(struct file *, char *, unsigned long, long long *)') with an expression of type 'ssize_t (struct file *, u8 *, size_t, loff_t *)' (aka 'long (struct file *, unsigned char *, unsigned long, long long *)') [-Werror,-Wincompatible-function-pointer-types]
.read = sisusb_read,
^~~~~~~~~~~
drivers/usb/misc/sisusbvga/sisusb.c:2997:11: error: incompatible function pointer types initializing 'ssize_t (*)(struct file *, const char *, size_t, loff_t *)' (aka 'long (*)(struct file *, const char *, unsigned long, long long *)') with an expression of type 'ssize_t (struct file *, const u8 *, size_t, loff_t *)' (aka 'long (struct file *, const unsigned char *, unsigned long, long long *)') [-Werror,-Wincompatible-function-pointer-types]
.write = sisusb_write,
^~~~~~~~~~~~
2 errors generated.
vim +2996 drivers/usb/misc/sisusbvga/sisusb.c
^1da177e4c3f41 Linus Torvalds 2005-04-16 2991
066202dd48cf32 Luiz Fernando N. Capitulino 2006-08-05 2992 static const struct file_operations usb_sisusb_fops = {
^1da177e4c3f41 Linus Torvalds 2005-04-16 2993 .owner = THIS_MODULE,
^1da177e4c3f41 Linus Torvalds 2005-04-16 2994 .open = sisusb_open,
^1da177e4c3f41 Linus Torvalds 2005-04-16 2995 .release = sisusb_release,
^1da177e4c3f41 Linus Torvalds 2005-04-16 @2996 .read = sisusb_read,
^1da177e4c3f41 Linus Torvalds 2005-04-16 2997 .write = sisusb_write,
^1da177e4c3f41 Linus Torvalds 2005-04-16 2998 .llseek = sisusb_lseek,
022e468e139573 Jiri Slaby 2019-01-22 2999 #ifdef CONFIG_COMPAT
^1da177e4c3f41 Linus Torvalds 2005-04-16 3000 .compat_ioctl = sisusb_compat_ioctl,
^1da177e4c3f41 Linus Torvalds 2005-04-16 3001 #endif
49f15255465321 Alan Cox 2008-05-22 3002 .unlocked_ioctl = sisusb_ioctl
^1da177e4c3f41 Linus Torvalds 2005-04-16 3003 };
^1da177e4c3f41 Linus Torvalds 2005-04-16 3004
:::::: The code at line 2996 was first introduced by commit
:::::: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Linux-2.6.12-rc2
:::::: TO: Linus Torvalds <torvalds@ppc970.osdl.org>
:::::: CC: Linus Torvalds <torvalds@ppc970.osdl.org>
---
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: 73536 bytes --]
next prev parent reply other threads:[~2020-05-31 22:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 1:48 [PATCH 0/6] USB: sisusbvga: series of changes char to u8 Changming
2020-05-30 1:48 ` [PATCH 1/6] USB: sisusbvga: change char to u8 for sisusb_copy_memory Changming
2020-05-30 1:48 ` [PATCH 2/6] USB: sisusbvga: change sisusb_write_mem_bulk Changming
2020-05-31 21:14 ` kbuild test robot
2020-05-31 21:35 ` kbuild test robot
2020-05-31 21:37 ` kbuild test robot
2020-05-30 1:48 ` [PATCH 3/6] USB: sisusbvga: change sisusb->ibuf,obuf,font_backup Changming
2020-05-30 1:48 ` [PATCH 4/6] USB: sisusbvga: change userbuffer for sisusb_recv_bulk_msg to u8 Changming
2020-05-30 1:48 ` [PATCH 5/6] USB: sisusbvga: change sisusb_read_mem_bulk Changming
2020-05-31 22:26 ` kbuild test robot
2020-05-31 22:43 ` kbuild test robot [this message]
2020-05-31 22:47 ` kbuild test robot
2020-05-30 1:48 ` [PATCH 6/6] USB: sisusbvga: change the local char array to u8 array Changming
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=202006010620.mYwc56Q1%lkp@intel.com \
--to=lkp@intel.com \
--cc=charley.ashbringer@gmail.com \
--cc=clang-built-linux@googlegroups.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-usb@vger.kernel.org \
--cc=liu.changm@northeastern.edu \
--cc=thomas@winischhofer.net \
/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