From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android16-6.12-2025-12 23/23] fs/binfmt_elf.c:2143:19: error: 'struct linux_binfmt' has no member named 'min_coredump'
Date: Sat, 18 Jul 2026 16:19:28 +0800 [thread overview]
Message-ID: <202607181640.NhtDPdk1-lkp@intel.com> (raw)
Hi Kalesh,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android16-6.12-2025-12
head: 921ffc45a309b3b476101d896d8aca3eca758ed9
commit: 58e2fa4ec4b1e15b7c7510bc98befafa31c03f70 [23/23] ANDROID: 16K: Remove build time dependencies on ELF_EXEC_PAGESIZE
config: i386-randconfig-015 (https://download.01.org/0day-ci/archive/20260718/202607181640.NhtDPdk1-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260718/202607181640.NhtDPdk1-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202607181640.NhtDPdk1-lkp@intel.com/
All errors (new ones prefixed by >>):
fs/binfmt_elf.c: In function 'init_elf_binfmt':
>> fs/binfmt_elf.c:2143:19: error: 'struct linux_binfmt' has no member named 'min_coredump'
2143 | elf_format.min_coredump = ELF_EXEC_PAGESIZE;
| ^
vim +2143 fs/binfmt_elf.c
2140
2141 static int __init init_elf_binfmt(void)
2142 {
> 2143 elf_format.min_coredump = ELF_EXEC_PAGESIZE;
2144 register_binfmt(&elf_format);
2145 return 0;
2146 }
2147
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-18 8:19 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=202607181640.NhtDPdk1-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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