From: kbuild test robot <lkp@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master] BUILD REGRESSION 5798bd75ab137611da5c4cb11b6795d14cb60ba2
Date: Thu, 09 Apr 2020 14:10:40 +0800 [thread overview]
Message-ID: <5e8ebc60.G9MN1K/QEElyw0Gp%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 5798bd75ab137611da5c4cb11b6795d14cb60ba2 Add linux-next specific files for 20200408
Error/Warning in current branch:
arch/x86/include/asm/fpu/xstate.h:50:29: warning: 'struct xregs_state' declared inside parameter list will not be visible outside of this definition or declaration
arch/x86/include/asm/fpu/xstate.h:59:48: warning: 'struct xstate_header' declared inside parameter list will not be visible outside of this definition or declaration
drivers/bluetooth/btusb.c:1665 btusb_work() error: we previously assumed 'data->isoc' could be null (see line 1642)
net/netfilter/nft_set_pipapo_avx2.c:1094:7: error: implicit declaration of function 'boot_cpu_has'; did you mean 'get_cpu_mask'? [-Werror=implicit-function-declaration]
Error/Warning ids grouped by kconfigs:
recent_errors
|-- i386-allyesconfig
| `-- drivers-bluetooth-btusb.c-btusb_work()-error:we-previously-assumed-data-isoc-could-be-null-(see-line-)
`-- um-allyesconfig
|-- arch-x86-include-asm-fpu-xstate.h:warning:struct-xregs_state-declared-inside-parameter-list-will-not-be-visible-outside-of-this-definition-or-declaration
|-- arch-x86-include-asm-fpu-xstate.h:warning:struct-xstate_header-declared-inside-parameter-list-will-not-be-visible-outside-of-this-definition-or-declaration
`-- net-netfilter-nft_set_pipapo_avx2.c:error:implicit-declaration-of-function-boot_cpu_has
elapsed time: 1509m
configs tested: 72
configs skipped: 50
arm64 allyesconfig
arm allyesconfig
arm64 allmodconfig
arm64 allnoconfig
arm allnoconfig
arm efm32_defconfig
arm at91_dt_defconfig
arm shmobile_defconfig
arm64 defconfig
arm exynos_defconfig
arm sunxi_defconfig
arm multi_v7_defconfig
arm multi_v5_defconfig
ia64 alldefconfig
i386 allnoconfig
ia64 allmodconfig
ia64 defconfig
ia64 allnoconfig
ia64 allyesconfig
arc defconfig
arc allyesconfig
powerpc defconfig
powerpc ppc64_defconfig
powerpc rhel-kconfig
microblaze mmu_defconfig
microblaze nommu_defconfig
powerpc allnoconfig
mips fuloong2e_defconfig
mips malta_kvm_defconfig
mips allyesconfig
mips 64r6el_defconfig
mips allnoconfig
mips 32r2_defconfig
mips allmodconfig
x86_64 randconfig-a003-20200408
i386 randconfig-a002-20200408
x86_64 randconfig-a001-20200408
x86_64 randconfig-a002-20200408
i386 randconfig-a003-20200408
i386 randconfig-a001-20200408
mips randconfig-a001-20200408
nds32 randconfig-a001-20200408
m68k randconfig-a001-20200408
alpha randconfig-a001-20200408
sparc64 randconfig-a001-20200408
s390 randconfig-a001-20200408
xtensa randconfig-a001-20200408
csky randconfig-a001-20200408
openrisc randconfig-a001-20200408
sh randconfig-a001-20200408
x86_64 randconfig-g003-20200408
i386 randconfig-g003-20200408
x86_64 randconfig-g002-20200408
i386 randconfig-g002-20200408
i386 randconfig-g001-20200408
i386 randconfig-h003-20200408
sparc randconfig-a001-20200408
arm64 randconfig-a001-20200408
ia64 randconfig-a001-20200408
arc randconfig-a001-20200408
arm randconfig-a001-20200408
sh rsk7269_defconfig
sh allmodconfig
sh titan_defconfig
sh sh7785lcr_32bit_defconfig
sh allnoconfig
i386 allyesconfig
x86_64 rhel
x86_64 rhel-7.2-clear
x86_64 lkp
x86_64 fedora-25
x86_64 kexec
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2020-04-09 6:11 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=5e8ebc60.G9MN1K/QEElyw0Gp%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.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