The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Wentao Guan <guanwentao@uniontech.com>, masahiroy@kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	petr.pavlu@suse.com, linux-kernel@vger.kernel.org,
	Wentao Guan <guanwentao@uniontech.com>
Subject: Re: [PATCH v2] genksyms: Support arm64 CRC32 hardware acceleration
Date: Thu, 28 May 2026 18:33:02 +0800	[thread overview]
Message-ID: <202605281815.1Z1xCVpw-lkp@intel.com> (raw)
In-Reply-To: <20260525070344.1564886-1-guanwentao@uniontech.com>

Hi Wentao,

kernel test robot noticed the following build warnings:

[auto build test WARNING on linus/master]
[also build test WARNING on v7.1-rc5 next-20260527]
[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/Wentao-Guan/genksyms-Support-arm64-CRC32-hardware-acceleration/20260525-151229
base:   linus/master
patch link:    https://lore.kernel.org/r/20260525070344.1564886-1-guanwentao%40uniontech.com
patch subject: [PATCH v2] genksyms: Support arm64 CRC32 hardware acceleration
config: um-randconfig-002 (https://download.01.org/0day-ci/archive/20260528/202605281815.1Z1xCVpw-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project 9409c07de6378507397ecdb6f05f628f58110112)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260528/202605281815.1Z1xCVpw-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/202605281815.1Z1xCVpw-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> scripts/genksyms/genksyms.c:122:12: warning: variable 'crc32_hw_available' set but not used [-Wunused-but-set-global]
     122 | static int crc32_hw_available;
         |            ^
   1 warning generated.
--
>> scripts/genksyms/genksyms.c:122:12: warning: variable 'crc32_hw_available' set but not used [-Wunused-but-set-global]
     122 | static int crc32_hw_available;
         |            ^
   1 warning generated.


vim +/crc32_hw_available +122 scripts/genksyms/genksyms.c

   118	
   119	/*
   120	 * Architecture-specific CRC32 hardware acceleration.
   121	 */
 > 122	static int crc32_hw_available;
   123	

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

      parent reply	other threads:[~2026-05-28 10:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-25  7:03 [PATCH v2] genksyms: Support arm64 CRC32 hardware acceleration Wentao Guan
2026-05-25  7:50 ` Petr Pavlu
2026-05-25  8:02   ` [PATCH v2] genksyms: Support arm64 CRC32 hardware acceleration1~ Wentao Guan
2026-05-25  9:09     ` Petr Pavlu
2026-05-25 13:41       ` Wentao Guan
2026-05-25 17:33         ` Petr Pavlu
2026-05-26 18:12           ` Wentao Guan
2026-05-26 19:13           ` Wentao Guan
2026-05-28 10:33 ` kernel test robot [this message]

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=202605281815.1Z1xCVpw-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=guanwentao@uniontech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=masahiroy@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=petr.pavlu@suse.com \
    /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