mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Bo Liu <liubo03@inspur.com>, xiang@kernel.org, chao@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, linux-erofs@lists.ozlabs.org,
	linux-kernel@vger.kernel.org, Bo Liu <liubo03@inspur.com>
Subject: Re: [PATCH v2] erofs: support deflate decompress by using Intel QAT
Date: Thu, 15 May 2025 09:44:38 +0800	[thread overview]
Message-ID: <202505150946.oGwqIzrW-lkp@intel.com> (raw)
In-Reply-To: <20250514121709.2557-1-liubo03@inspur.com>

Hi Bo,

kernel test robot noticed the following build warnings:

[auto build test WARNING on xiang-erofs/dev-test]
[also build test WARNING on xiang-erofs/dev xiang-erofs/fixes linus/master v6.15-rc6 next-20250514]
[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/Bo-Liu/erofs-support-deflate-decompress-by-using-Intel-QAT/20250514-202351
base:   https://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git dev-test
patch link:    https://lore.kernel.org/r/20250514121709.2557-1-liubo03%40inspur.com
patch subject: [PATCH v2] erofs: support deflate decompress by using Intel QAT
config: riscv-randconfig-002-20250515 (https://download.01.org/0day-ci/archive/20250515/202505150946.oGwqIzrW-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250515/202505150946.oGwqIzrW-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/202505150946.oGwqIzrW-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> fs/erofs/decompressor_crypto.c:211:9: warning: braces around scalar initializer
     211 |         [Z_EROFS_COMPRESSION_DEFLATE] = {&(struct z_erofs_crypto_engine) {
         |         ^
   fs/erofs/decompressor_crypto.c:211:9: note: (near initialization for 'z_erofs_crypto[2]')
   fs/erofs/decompressor_crypto.c:216:17: warning: excess elements in scalar initializer
     216 |                 &(const struct z_erofs_crypto_engine) { NULL },
         |                 ^
   fs/erofs/decompressor_crypto.c:216:17: note: (near initialization for 'z_erofs_crypto[2]')


vim +211 fs/erofs/decompressor_crypto.c

   207	
   208	struct z_erofs_crypto_engine *z_erofs_crypto[] = {
   209		[Z_EROFS_COMPRESSION_LZ4] = &(struct z_erofs_crypto_engine) {NULL},
   210		[Z_EROFS_COMPRESSION_LZMA] = &(struct z_erofs_crypto_engine) {NULL},
 > 211		[Z_EROFS_COMPRESSION_DEFLATE] = {&(struct z_erofs_crypto_engine) {

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

  reply	other threads:[~2025-05-15  1:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-14 12:17 Bo Liu
2025-05-15  1:44 ` kernel test robot [this message]
2025-05-15  2:59 ` kernel test robot
     [not found] ` <001d2160-e999-43cd-8bf1-2507e4a4eb1d@huawei.com>
2025-05-15  5:12   ` Gao Xiang

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=202505150946.oGwqIzrW-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=chao@kernel.org \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liubo03@inspur.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=xiang@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

all inboxes | Powered by JetHome®