From: kernel test robot <lkp@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:pending-fixes] BUILD REGRESSION 8562c805780e79133c8b4e03d52a91eaf4fe7214
Date: Thu, 17 Sep 2020 05:39:26 +0800 [thread overview]
Message-ID: <5f62860e.OycFd+2xzuJeVyqq%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git pending-fixes
branch HEAD: 8562c805780e79133c8b4e03d52a91eaf4fe7214 Merge remote-tracking branch 'drm-misc-fixes/for-linux-next-fixes' into master
Error/Warning in current branch:
{standard input}:5081: Error: operand out of range (512 is not between -512 and 511)
Error/Warning ids grouped by kconfigs:
gcc_recent_errors
`-- arc-randconfig-r005-20200916
`-- standard-input:Error:operand-out-of-range-(-is-not-between-and-)
elapsed time: 759m
configs tested: 98
configs skipped: 2
gcc tested configs:
arm allmodconfig
arm defconfig
arm64 allyesconfig
arm64 defconfig
arm allyesconfig
mips decstation_defconfig
mips malta_kvm_defconfig
sh sh7763rdp_defconfig
arm pcm027_defconfig
powerpc storcenter_defconfig
mips cobalt_defconfig
i386 alldefconfig
powerpc tqm5200_defconfig
m68k m5407c3_defconfig
mips loongson1c_defconfig
powerpc holly_defconfig
mips maltaaprp_defconfig
xtensa xip_kc705_defconfig
arm spear6xx_defconfig
mips jazz_defconfig
powerpc rainier_defconfig
powerpc ppc64e_defconfig
powerpc pq2fads_defconfig
sh rsk7269_defconfig
mips db1xxx_defconfig
mips rb532_defconfig
powerpc tqm8xx_defconfig
powerpc katmai_defconfig
sh apsh4ad0a_defconfig
powerpc wii_defconfig
arm exynos_defconfig
ia64 bigsur_defconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
c6x allyesconfig
nds32 defconfig
nios2 allyesconfig
csky defconfig
alpha defconfig
alpha allyesconfig
xtensa allyesconfig
h8300 allyesconfig
arc defconfig
sh allmodconfig
parisc defconfig
s390 allyesconfig
parisc allyesconfig
s390 defconfig
i386 allyesconfig
sparc allyesconfig
sparc defconfig
i386 defconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
x86_64 randconfig-a006-20200916
x86_64 randconfig-a004-20200916
x86_64 randconfig-a003-20200916
x86_64 randconfig-a002-20200916
x86_64 randconfig-a001-20200916
x86_64 randconfig-a005-20200916
i386 randconfig-a004-20200916
i386 randconfig-a006-20200916
i386 randconfig-a003-20200916
i386 randconfig-a001-20200916
i386 randconfig-a002-20200916
i386 randconfig-a005-20200916
i386 randconfig-a015-20200916
i386 randconfig-a014-20200916
i386 randconfig-a011-20200916
i386 randconfig-a013-20200916
i386 randconfig-a016-20200916
i386 randconfig-a012-20200916
riscv allyesconfig
riscv allnoconfig
riscv defconfig
riscv allmodconfig
x86_64 rhel
x86_64 allyesconfig
x86_64 rhel-7.6-kselftests
x86_64 defconfig
x86_64 rhel-8.3
x86_64 kexec
clang tested configs:
x86_64 randconfig-a014-20200916
x86_64 randconfig-a011-20200916
x86_64 randconfig-a016-20200916
x86_64 randconfig-a012-20200916
x86_64 randconfig-a015-20200916
x86_64 randconfig-a013-20200916
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2020-09-16 21:39 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=5f62860e.OycFd+2xzuJeVyqq%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