From: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: drivers/md/dm-vdo/int-map.c:85: error: Cannot parse struct or union!
Date: Mon, 27 May 2024 23:37:17 +0800 [thread overview]
Message-ID: <202405272334.ExNaB8F6-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0
commit: 0d21364c6e8dc1f62c34bbc49d49935c8b01844c Merge drm/drm-next into drm-misc-next
date: 8 weeks ago
config: sparc64-allyesconfig (https://download.01.org/0day-ci/archive/20240527/202405272334.ExNaB8F6-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/20240527/202405272334.ExNaB8F6-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/202405272334.ExNaB8F6-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/md/dm-vdo/int-map.c:85: error: Cannot parse struct or union!
drivers/md/dm-vdo/int-map.c:103: warning: Function parameter or struct member 'bucket_count' not described in 'int_map'
drivers/md/dm-vdo/int-map.c:328: warning: Function parameter or struct member '__always_unused' not described in 'search_hop_list'
drivers/md/dm-vdo/int-map.c:328: warning: Excess function parameter 'map' description in 'search_hop_list'
drivers/md/dm-vdo/int-map.c:459: warning: Function parameter or struct member '__always_unused' not described in 'move_empty_bucket'
drivers/md/dm-vdo/int-map.c:459: warning: Excess function parameter 'map' description in 'move_empty_bucket'
vim +85 drivers/md/dm-vdo/int-map.c
cc46b9554b3f6d Matthew Sakai 2023-11-16 64
cc46b9554b3f6d Matthew Sakai 2023-11-16 65 /**
cc46b9554b3f6d Matthew Sakai 2023-11-16 66 * struct bucket - hash bucket
cc46b9554b3f6d Matthew Sakai 2023-11-16 67 *
cc46b9554b3f6d Matthew Sakai 2023-11-16 68 * Buckets are packed together to reduce memory usage and improve cache efficiency. It would be
cc46b9554b3f6d Matthew Sakai 2023-11-16 69 * tempting to encode the hop offsets separately and maintain alignment of key/value pairs, but
cc46b9554b3f6d Matthew Sakai 2023-11-16 70 * it's crucial to keep the hop fields near the buckets that they use them so they'll tend to share
cc46b9554b3f6d Matthew Sakai 2023-11-16 71 * cache lines.
cc46b9554b3f6d Matthew Sakai 2023-11-16 72 */
cc46b9554b3f6d Matthew Sakai 2023-11-16 73 struct __packed bucket {
cc46b9554b3f6d Matthew Sakai 2023-11-16 74 /**
cc46b9554b3f6d Matthew Sakai 2023-11-16 75 * @first_hop: The biased offset of the first entry in the hop list of the neighborhood
cc46b9554b3f6d Matthew Sakai 2023-11-16 76 * that hashes to this bucket.
cc46b9554b3f6d Matthew Sakai 2023-11-16 77 */
cc46b9554b3f6d Matthew Sakai 2023-11-16 78 u8 first_hop;
cc46b9554b3f6d Matthew Sakai 2023-11-16 79 /** @next_hop: The biased offset of the next bucket in the hop list. */
cc46b9554b3f6d Matthew Sakai 2023-11-16 80 u8 next_hop;
cc46b9554b3f6d Matthew Sakai 2023-11-16 81 /** @key: The key stored in this bucket. */
cc46b9554b3f6d Matthew Sakai 2023-11-16 82 u64 key;
cc46b9554b3f6d Matthew Sakai 2023-11-16 83 /** @value: The value stored in this bucket (NULL if empty). */
cc46b9554b3f6d Matthew Sakai 2023-11-16 84 void *value;
cc46b9554b3f6d Matthew Sakai 2023-11-16 @85 };
cc46b9554b3f6d Matthew Sakai 2023-11-16 86
:::::: The code at line 85 was first introduced by commit
:::::: cc46b9554b3f6d2f09b1111386b2706e5b4f56c8 dm vdo: add basic hash map data structures
:::::: TO: Matthew Sakai <msakai@redhat.com>
:::::: CC: Mike Snitzer <snitzer@kernel.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-05-27 15:37 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=202405272334.ExNaB8F6-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tzimmermann@suse.de \
/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®