public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Borislav Petkov <bp@kernel.org>, Josh Poimboeuf <jpoimboe@kernel.org>
Cc: <oe-kbuild-all@lists.linux.dev>, X86 ML <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Borislav Petkov (AMD)" <bp@alien8.de>
Subject: Re: [PATCH] objtool/klp: Add the debian-based package name of xxhash to the hint
Date: Sun, 19 Oct 2025 13:07:22 +0800	[thread overview]
Message-ID: <aPRyCq55erNhA8CI@rli9-mobl> (raw)
In-Reply-To: <20251017194732.7713-1-bp@kernel.org>

Hi Borislav,

kernel test robot noticed the following build errors:

[auto build test ERROR on next-20251017]
[cannot apply to linus/master v6.18-rc1 v6.17 v6.17-rc7 v6.18-rc1]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Borislav-Petkov/objtool-klp-Add-the-debian-based-package-name-of-xxhash-to-the-hint/20251018-091553
base:   next-20251017
patch link:    https://lore.kernel.org/r/20251017194732.7713-1-bp%40kernel.org
patch subject: [PATCH] objtool/klp: Add the debian-based package name of xxhash to the hint
:::::: branch date: 25 hours ago
:::::: commit date: 25 hours ago
config: x86_64-rhel-9.4 (https://download.01.org/0day-ci/archive/20251019/202510190931.1SovbysA-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/20251019/202510190931.1SovbysA-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/202510190931.1SovbysA-lkp@intel.com/

All errors (new ones prefixed by >>):

>> error: objtool: --checksum not supported; install xxhash-devel/libxxhash-dev and recompile
--
   drivers/message/fusion/mptsas.c: In function 'mptsas_issue_tm':
   drivers/message/fusion/mptsas.c:4791:26: warning: variable 'timeleft' set but not used [-Wunused-but-set-variable]
    4791 |         unsigned long    timeleft;
         |                          ^~~~~~~~
>> error: objtool: --checksum not supported; install xxhash-devel/libxxhash-dev and recompile
--
   mptsas.c: In function 'mptsas_issue_tm':
   mptsas.c:4791:26: warning: variable 'timeleft' set but not used [-Wunused-but-set-variable]
    4791 |         unsigned long    timeleft;
         |                          ^~~~~~~~
>> error: objtool: --checksum not supported; install xxhash-devel/libxxhash-dev and recompile

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


  reply	other threads:[~2025-10-19  5:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-17 19:47 [PATCH] objtool/klp: Add the debian-based package name of xxhash to the hint Borislav Petkov
2025-10-19  5:07 ` kernel test robot [this message]
2025-10-19  5:11   ` Philip Li
2025-10-22 12:01 ` [tip: objtool/core] " tip-bot2 for Borislav Petkov (AMD)

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=aPRyCq55erNhA8CI@rli9-mobl \
    --to=lkp@intel.com \
    --cc=bp@alien8.de \
    --cc=bp@kernel.org \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=x86@kernel.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