linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:pending-fixes] BUILD SUCCESS WITH WARNING ef5b2e74bc50799a4e8b962a34971c8a593af37a
Date: Wed, 09 Nov 2022 05:49:54 +0800	[thread overview]
Message-ID: <636acf02.7E3065pTrVLOwGnL%lkp@intel.com> (raw)

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git pending-fixes
branch HEAD: ef5b2e74bc50799a4e8b962a34971c8a593af37a  Merge branch 'for-linux-next-fixes' of git://anongit.freedesktop.org/drm/drm-misc

Warning: (recently discovered and may have been fixed)

lib/test_maple_tree.c:453:12: warning: result of comparison of constant 4398046511104 with expression of type 'unsigned long' is always false [-Wtautological-constant-out-of-range-compare]

Warning ids grouped by kconfigs:

clang_recent_errors
`-- arm-buildonly-randconfig-r001-20221108
    `-- lib-test_maple_tree.c:warning:result-of-comparison-of-constant-with-expression-of-type-unsigned-long-is-always-false

elapsed time: 1444m

configs tested: 42
configs skipped: 4

gcc tested configs:
um                           x86_64_defconfig
powerpc                           allnoconfig
arc                  randconfig-r043-20221107
ia64                             allmodconfig
sh                               allmodconfig
x86_64                              defconfig
powerpc                          allmodconfig
mips                             allyesconfig
x86_64                           rhel-8.3-kvm
x86_64                           rhel-8.3-syz
x86_64                               rhel-8.3
x86_64                         rhel-8.3-kunit
x86_64                           allyesconfig
arc                                 defconfig
s390                             allmodconfig
s390                                defconfig
i386                             allyesconfig
i386                                defconfig
arm64                            allyesconfig
arm                                 defconfig
arm                              allyesconfig
um                             i386_defconfig
m68k                             allyesconfig
m68k                             allmodconfig
arc                              allyesconfig
alpha                            allyesconfig
x86_64                        randconfig-a011
alpha                               defconfig
x86_64                        randconfig-a013
x86_64                        randconfig-a015

clang tested configs:
hexagon              randconfig-r041-20221107
riscv                randconfig-r042-20221107
s390                 randconfig-r044-20221107
hexagon              randconfig-r045-20221107
x86_64               randconfig-a012-20221107
x86_64               randconfig-a011-20221107
x86_64               randconfig-a014-20221107
x86_64               randconfig-a013-20221107
x86_64               randconfig-a015-20221107
x86_64                        randconfig-a012
x86_64                        randconfig-a016
x86_64                        randconfig-a014

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp


                 reply	other threads:[~2022-11-08 21:51 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=636acf02.7E3065pTrVLOwGnL%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