From: kernel test robot <lkp@intel.com>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org
Subject: [usb:usb-linus] BUILD SUCCESS WITH WARNING a8c67e27d9e3ed33afadbdf86bbd58e26e0c4357
Date: Sat, 20 Aug 2022 05:56:25 +0800 [thread overview]
Message-ID: <63000709.79x4DAEU+D2F+Dx6%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-linus
branch HEAD: a8c67e27d9e3ed33afadbdf86bbd58e26e0c4357 dt-bindings: usb: mtu3: add compatible for mt8188
Warning reports:
https://lore.kernel.org/linux-usb/202208190411.1lugjsYz-lkp@intel.com
Warning: (recently discovered and may have been fixed)
drivers/usb/dwc3/dwc3-qcom.c:313:25: warning: variable 'hcd' set but not used [-Wunused-but-set-variable]
Warning ids grouped by kconfigs:
gcc_recent_errors
|-- alpha-allmodconfig
| `-- drivers-usb-dwc3-dwc3-qcom.c:warning:variable-hcd-set-but-not-used
|-- ia64-allmodconfig
| `-- drivers-usb-dwc3-dwc3-qcom.c:warning:variable-hcd-set-but-not-used
|-- m68k-allmodconfig
| `-- drivers-usb-dwc3-dwc3-qcom.c:warning:variable-hcd-set-but-not-used
|-- mips-allmodconfig
| `-- drivers-usb-dwc3-dwc3-qcom.c:warning:variable-hcd-set-but-not-used
|-- powerpc-allmodconfig
| `-- drivers-usb-dwc3-dwc3-qcom.c:warning:variable-hcd-set-but-not-used
`-- riscv-allmodconfig
`-- drivers-usb-dwc3-dwc3-qcom.c:warning:variable-hcd-set-but-not-used
elapsed time: 720m
configs tested: 53
configs skipped: 2
gcc tested configs:
um i386_defconfig
um x86_64_defconfig
i386 defconfig
arm defconfig
arc allyesconfig
alpha allyesconfig
x86_64 randconfig-a013
x86_64 randconfig-a011
i386 randconfig-a001
i386 randconfig-a003
x86_64 defconfig
arc randconfig-r043-20220819
i386 randconfig-a005
x86_64 randconfig-a015
x86_64 rhel-8.3
x86_64 allyesconfig
x86_64 randconfig-a004
x86_64 randconfig-a002
m68k allyesconfig
m68k allmodconfig
i386 randconfig-a014
x86_64 randconfig-a006
i386 randconfig-a012
i386 randconfig-a016
powerpc allmodconfig
mips allyesconfig
powerpc allnoconfig
x86_64 rhel-8.3-kselftests
arm64 allyesconfig
i386 allyesconfig
sh allmodconfig
x86_64 rhel-8.3-syz
x86_64 rhel-8.3-func
arm allyesconfig
x86_64 rhel-8.3-kunit
x86_64 rhel-8.3-kvm
ia64 allmodconfig
clang tested configs:
hexagon randconfig-r045-20220819
hexagon randconfig-r041-20220819
x86_64 randconfig-a012
i386 randconfig-a002
riscv randconfig-r042-20220819
s390 randconfig-r044-20220819
x86_64 randconfig-a014
x86_64 randconfig-a016
i386 randconfig-a004
i386 randconfig-a006
x86_64 randconfig-a005
i386 randconfig-a013
x86_64 randconfig-a001
i386 randconfig-a011
x86_64 randconfig-a003
i386 randconfig-a015
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-08-19 21:57 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=63000709.79x4DAEU+D2F+Dx6%lkp@intel.com \
--to=lkp@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@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