From: kernel test robot <lkp@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-bluetooth@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:pending-fixes] BUILD SUCCESS 72d0e40cc07e06e5b11ddcf74ba68f7e04eacb16
Date: Mon, 22 Aug 2022 20:04:57 +0800 [thread overview]
Message-ID: <630370e9.lrkhEwYdtnOT++I7%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git pending-fixes
branch HEAD: 72d0e40cc07e06e5b11ddcf74ba68f7e04eacb16 Merge branch 'for-linux-next-fixes' of git://anongit.freedesktop.org/drm/drm-misc
Unverified Warning (likely false positive, please contact us if interested):
drivers/usb/dwc3/dwc3-qcom.c:313:25: warning: variable 'hcd' set but not used [-Wunused-but-set-variable]
include/net/bluetooth/bluetooth.h:347:16: warning: 'memcmp' specified bound 6 exceeds source size 0 [-Wstringop-overread]
Warning ids grouped by kconfigs:
gcc_recent_errors
|-- ia64-allmodconfig
| `-- drivers-usb-dwc3-dwc3-qcom.c:warning:variable-hcd-set-but-not-used
|-- openrisc-buildonly-randconfig-r006-20220821
| `-- include-net-bluetooth-bluetooth.h:warning:memcmp-specified-bound-exceeds-source-size
|-- openrisc-randconfig-r021-20220821
| `-- include-net-bluetooth-bluetooth.h:warning:memcmp-specified-bound-exceeds-source-size
`-- sparc64-buildonly-randconfig-r003-20220822
`-- drivers-usb-dwc3-dwc3-qcom.c:warning:variable-hcd-set-but-not-used
elapsed time: 723m
configs tested: 63
configs skipped: 2
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
um i386_defconfig
um x86_64_defconfig
i386 randconfig-a014-20220822
i386 randconfig-a013-20220822
i386 randconfig-a011-20220822
arm defconfig
i386 randconfig-a012-20220822
arc allnoconfig
x86_64 rhel-8.3-func
alpha allnoconfig
x86_64 rhel-8.3-kunit
i386 randconfig-a015-20220822
arm allyesconfig
x86_64 rhel-8.3-kvm
x86_64 defconfig
riscv allnoconfig
x86_64 rhel-8.3
x86_64 randconfig-a012-20220822
x86_64 rhel-8.3-kselftests
i386 randconfig-a016-20220822
x86_64 randconfig-a013-20220822
x86_64 rhel-8.3-syz
i386 randconfig-a001
arc randconfig-r043-20220821
csky allnoconfig
x86_64 randconfig-a011-20220822
arm64 allyesconfig
arc randconfig-r043-20220822
riscv randconfig-r042-20220822
i386 randconfig-a003
x86_64 randconfig-a016-20220822
x86_64 randconfig-a014-20220822
i386 randconfig-a005
x86_64 allyesconfig
arc allyesconfig
alpha allyesconfig
m68k allyesconfig
s390 randconfig-r044-20220822
m68k allmodconfig
x86_64 randconfig-a015-20220822
powerpc allmodconfig
mips allyesconfig
powerpc allnoconfig
sh allmodconfig
ia64 allmodconfig
i386 defconfig
i386 allyesconfig
clang tested configs:
x86_64 randconfig-a002-20220822
x86_64 randconfig-a005-20220822
x86_64 randconfig-a004-20220822
x86_64 randconfig-a003-20220822
hexagon randconfig-r041-20220822
x86_64 randconfig-a001-20220822
hexagon randconfig-r045-20220822
x86_64 randconfig-a006-20220822
i386 randconfig-a002
riscv randconfig-r042-20220821
i386 randconfig-a004
hexagon randconfig-r045-20220821
hexagon randconfig-r041-20220821
s390 randconfig-r044-20220821
i386 randconfig-a006
x86_64 rhel-8.3-rust
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-08-22 12:05 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=630370e9.lrkhEwYdtnOT++I7%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-mm@kvack.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