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 6ec8e62a9eab8f2a9e9ba51d9164c18a9117c766
Date: Sat, 08 Jun 2024 13:08:56 +0800 [thread overview]
Message-ID: <202406081353.8iTuS9nQ-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git pending-fixes
branch HEAD: 6ec8e62a9eab8f2a9e9ba51d9164c18a9117c766 Merge branch 'for-linux-next-fixes' of https://gitlab.freedesktop.org/drm/misc/kernel.git
Error/Warning ids grouped by kconfigs:
gcc_recent_errors
`-- mips-allyesconfig
|-- (.ref.text):relocation-truncated-to-fit:R_MIPS_26-against-start_secondary
`-- (.text):relocation-truncated-to-fit:R_MIPS_26-against-kernel_entry
elapsed time: 1456m
configs tested: 29
configs skipped: 2
tested configs:
alpha allyesconfig gcc
hexagon allmodconfig clang
hexagon allyesconfig clang
i386 buildonly-randconfig-001-20240608 gcc
i386 buildonly-randconfig-002-20240608 clang
i386 buildonly-randconfig-003-20240608 gcc
i386 buildonly-randconfig-004-20240608 gcc
openrisc allnoconfig gcc
openrisc defconfig gcc
parisc allnoconfig gcc
parisc defconfig gcc
parisc64 defconfig gcc
powerpc allnoconfig gcc
riscv allnoconfig gcc
riscv defconfig clang
s390 allnoconfig clang
s390 defconfig clang
sh allnoconfig gcc
sh defconfig gcc
sparc allnoconfig gcc
sparc defconfig gcc
sparc64 defconfig gcc
um allmodconfig clang
um allnoconfig clang
um allyesconfig gcc
um defconfig clang
um i386_defconfig gcc
um x86_64_defconfig clang
xtensa allnoconfig gcc
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-06-08 5:09 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=202406081353.8iTuS9nQ-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