All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Matthew Sakai <msakai@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v4 39/39] dm vdo: enable configuration and building of dm-vdo
Date: Fri, 27 Oct 2023 19:39:27 +0800	[thread overview]
Message-ID: <202310271945.092XwBE0-lkp@intel.com> (raw)
In-Reply-To: <20231026214136.1067410-40-msakai@redhat.com>

Hi Matthew,

kernel test robot noticed the following build warnings:

[auto build test WARNING on 1e4ab7b4c881cf26c1c72b3f56519e03475486fb]

url:    https://github.com/intel-lab-lkp/linux/commits/Matthew-Sakai/dm-add-documentation-for-dm-vdo-target/20231027-054713
base:   1e4ab7b4c881cf26c1c72b3f56519e03475486fb
patch link:    https://lore.kernel.org/r/20231026214136.1067410-40-msakai%40redhat.com
patch subject: [PATCH v4 39/39] dm vdo: enable configuration and building of dm-vdo
config: sparc-allyesconfig (https://download.01.org/0day-ci/archive/20231027/202310271945.092XwBE0-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231027/202310271945.092XwBE0-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/202310271945.092XwBE0-lkp@intel.com/

All warnings (new ones prefixed by >>):

   In file included from drivers/md/dm-vdo-target.c:16:
>> drivers/md/dm-vdo/block-map.h:35:37: warning: 'UNMAPPED_BLOCK_MAP_ENTRY' defined but not used [-Wunused-const-variable=]
      35 | static const struct block_map_entry UNMAPPED_BLOCK_MAP_ENTRY = {
         |                                     ^~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/md/dm-vdo/block-map.h:34:38: warning: 'NO_PAGE' defined but not used [-Wunused-const-variable=]
      34 | static const physical_block_number_t NO_PAGE = 0xFFFFFFFFFFFFFFFF;
         |                                      ^~~~~~~
--
>> drivers/md/dm-vdo-target.c:1162: warning: Function parameter or member 'vdo' not described in 'get_thread_id_for_phase'


vim +/UNMAPPED_BLOCK_MAP_ENTRY +35 drivers/md/dm-vdo/block-map.h

13d47b7579638e Matthew Sakai 2023-10-26  33  
397119f4a6191f Matthew Sakai 2023-10-26 @34  static const physical_block_number_t NO_PAGE = 0xFFFFFFFFFFFFFFFF;
397119f4a6191f Matthew Sakai 2023-10-26 @35  static const struct block_map_entry UNMAPPED_BLOCK_MAP_ENTRY = {
397119f4a6191f Matthew Sakai 2023-10-26  36  	.mapping_state = VDO_MAPPING_STATE_UNMAPPED & 0x0F,
397119f4a6191f Matthew Sakai 2023-10-26  37  	.pbn_high_nibble = 0,
397119f4a6191f Matthew Sakai 2023-10-26  38  	.pbn_low_word = __cpu_to_le32(VDO_ZERO_BLOCK & UINT_MAX),
397119f4a6191f Matthew Sakai 2023-10-26  39  };
397119f4a6191f Matthew Sakai 2023-10-26  40  

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

  reply	other threads:[~2023-10-27 11:40 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26 21:40 [PATCH v4 00/39] dm vdo: add the dm-vdo deduplication and compression DM target Matthew Sakai
2023-10-26 21:40 ` [PATCH v4 01/39] dm: add documentation for dm-vdo target Matthew Sakai
2023-10-26 21:40 ` [PATCH v4 02/39] dm vdo: add the MurmurHash3 fast hashing algorithm Matthew Sakai
2024-03-14 23:35   ` Guenter Roeck
2024-03-18 20:37     ` Kenneth Raeburn
2024-03-18 20:54       ` Guenter Roeck
2024-03-19  1:14         ` Matthew Sakai
2024-03-20 21:44         ` Matthew Sakai
2024-03-20 22:59           ` Guenter Roeck
2023-10-26 21:41 ` [PATCH v4 03/39] dm vdo: add memory allocation utilities Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 04/39] dm vdo: add basic logging and support utilities Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 05/39] dm vdo: add vdo type declarations, constants, and simple data structures Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 06/39] dm vdo: add thread and synchronization utilities Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 07/39] dm vdo: add specialized request queueing functionality Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 08/39] dm vdo: add basic hash map data structures Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 09/39] dm vdo: add deduplication configuration structures Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 10/39] dm vdo: add deduplication index storage interface Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 11/39] dm vdo: implement the delta index Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 12/39] dm vdo: implement the volume index Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 13/39] dm vdo: implement the open chapter and chapter indexes Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 14/39] dm vdo: implement the chapter volume store Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 15/39] dm vdo: implement top-level deduplication index Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 16/39] dm vdo: implement external deduplication index interface Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 17/39] dm vdo: add administrative state and action manager Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 18/39] dm vdo: add vio, the request object for vdo metadata Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 19/39] dm vdo: add data_vio, the request object which services incoming bios Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 20/39] dm vdo: add flush support Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 21/39] dm vdo: add the vdo io_submitter Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 22/39] dm vdo: add hash locks and hash zones Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 23/39] dm vdo: add use of deduplication index in " Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 24/39] dm vdo: add the compressed block bin packer Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 25/39] dm vdo: add slab structure, slab journal and reference counters Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 26/39] dm vdo: add the slab summary Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 27/39] dm vdo: add the block allocators and physical zones Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 28/39] dm vdo: add the slab depot Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 29/39] dm vdo: add the block map Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 30/39] dm vdo: implement the block map page cache Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 31/39] dm vdo: add the recovery journal Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 32/39] dm vdo: add repair of damaged vdo volumes Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 33/39] dm vdo: add the primary vdo structure Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 34/39] dm vdo: add the on-disk formats and marshalling of vdo structures Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 35/39] dm vdo: add statistics reporting Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 36/39] dm vdo: add sysfs support for setting parameters and fetching stats Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 37/39] dm vdo: add debugging support Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 38/39] dm vdo: add the top-level DM target Matthew Sakai
2023-10-26 21:41 ` [PATCH v4 39/39] dm vdo: enable configuration and building of dm-vdo Matthew Sakai
2023-10-27 11:39   ` kernel test robot [this message]
2023-10-30  8:07   ` kernel test robot
2023-10-30 22:25   ` kernel test robot
2023-11-01 18:28 ` [PATCH v4 00/39] dm vdo: add the dm-vdo deduplication and compression DM target Mike Snitzer

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=202310271945.092XwBE0-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=msakai@redhat.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 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.