From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [gourryinverse:scratch/gourry/managed_nodes/rfc6-nonuma 43/51] cram_perf_tool.c:289:13: error: implicit declaration of function 'cram_pageout'
Date: Sun, 27 Sep 2026 12:08:33 +0200 [thread overview]
Message-ID: <202609271232.JQGSshY2-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence bisect report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: Gregory Price <gourry@gourry.net>
TO: Gregory Price <gourry@gourry.net>
tree: https://github.com/gourryinverse/linux scratch/gourry/managed_nodes/rfc6-nonuma
head: f1fcedacbd06c5213a7e01f7a087588e24b47a61
commit: ddcbe8cef481b29f8349e19ca7be93e2023e6bbf [43/51] selftests/dax: benchmark CRAM fault behavior
:::::: branch date: 2 days ago
:::::: commit date: 2 days ago
config: s390-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260927/202609271232.JQGSshY2-lkp@intel.com/config)
compiler: s390x-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260927/202609271232.JQGSshY2-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/r/202609271232.JQGSshY2-lkp@intel.com/
Note: the gourryinverse/scratch/gourry/managed_nodes/rfc6-nonuma HEAD f1fcedacbd06c5213a7e01f7a087588e24b47a61 builds fine.
It only hurts bisectability.
All errors (new ones prefixed by >>):
cram_perf_tool.c: In function 'arm_batch':
>> cram_perf_tool.c:289:13: error: implicit declaration of function 'cram_pageout' [-Wimplicit-function-declaration]
289 | if (cram_pageout(p, len))
| ^~~~~~~~~~~~
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-27 10:08 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=202609271232.JQGSshY2-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.