From: kernel test robot <lkp@intel.com>
To: Anurag Kumar Vulisha <anurag.kumar.vulisha@xilinx.com>
Cc: clang-built-linux@googlegroups.com, kbuild-all@lists.01.org,
linux-arm-kernel@lists.infradead.org,
Michal Simek <monstr@monstr.eu>,
Piyush Mehta <piyush.mehta@xilinx.com>
Subject: [xlnx:master 11279/12317] drivers/usb/gadget/function/f_tcm.c:2262:12: error: redefinition of 'tcm_get_alt'
Date: Thu, 8 Jul 2021 10:30:08 +0800 [thread overview]
Message-ID: <202107081001.dp6VcNaL-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2297 bytes --]
Hi Anurag,
FYI, the error/warning still remains.
tree: https://github.com/Xilinx/linux-xlnx master
head: d25c42dcc2a9fed0d00f4f20eded4aa733d51d5b
commit: c327a8947017ebe78c31d8018092a91b540dab8c [11279/12317] usb: function: f_tcm: Add support for getting alt interface number
config: x86_64-randconfig-a015-20210707 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project 8d69635ed9ecf36fd0ca85906bfde17949671cbe)
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
# https://github.com/Xilinx/linux-xlnx/commit/c327a8947017ebe78c31d8018092a91b540dab8c
git remote add xlnx https://github.com/Xilinx/linux-xlnx
git fetch --no-tags xlnx master
git checkout c327a8947017ebe78c31d8018092a91b540dab8c
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross O=build_dir ARCH=x86_64 SHELL=/bin/bash
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/usb/gadget/function/f_tcm.c:342:12: warning: address of array 'fu->cmd' will always evaluate to 'true' [-Wpointer-bool-conversion]
if (!fu->cmd)
~~~~~^~~
>> drivers/usb/gadget/function/f_tcm.c:2262:12: error: redefinition of 'tcm_get_alt'
static int tcm_get_alt(struct usb_function *f, unsigned int intf)
^
drivers/usb/gadget/function/f_tcm.c:2233:12: note: previous definition is here
static int tcm_get_alt(struct usb_function *f, unsigned intf)
^
1 warning and 1 error generated.
vim +/tcm_get_alt +2262 drivers/usb/gadget/function/f_tcm.c
2261
> 2262 static int tcm_get_alt(struct usb_function *f, unsigned int intf)
2263 {
2264 struct f_uas *fu = to_f_uas(f);
2265
2266 return fu->flags & USBG_IS_UAS ? 1 : 0;
2267 }
2268
---
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: 49436 bytes --]
[-- Attachment #3: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2021-07-08 2:33 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=202107081001.dp6VcNaL-lkp@intel.com \
--to=lkp@intel.com \
--cc=anurag.kumar.vulisha@xilinx.com \
--cc=clang-built-linux@googlegroups.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=monstr@monstr.eu \
--cc=piyush.mehta@xilinx.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).