From: kernel test robot <lkp@intel.com>
To: Jim Cromie <jim.cromie@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jimc:maph 6/7] lib/test_map_h.c:32:13: warning: 'MAPH_BUILD_BUG' defined but not used
Date: Wed, 23 Aug 2023 21:51:47 +0800 [thread overview]
Message-ID: <202308232127.6vsYZhdm-lkp@intel.com> (raw)
tree: https://github.com/jimc/linux.git maph
head: 7f5a5e57c1ce6971acdfa13d3e177b14fe615838
commit: 3acf936f65d59ef4588b1c10924acc77c157b205 [6/7] strip-used-MAPH-BB
config: arm-randconfig-001-20230822 (https://download.01.org/0day-ci/archive/20230823/202308232127.6vsYZhdm-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230823/202308232127.6vsYZhdm-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/202308232127.6vsYZhdm-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> lib/test_map_h.c:32:13: warning: 'MAPH_BUILD_BUG' defined but not used [-Wunused-function]
32 | static void MAPH_BUILD_BUG(void)
| ^~~~~~~~~~~~~~
vim +/MAPH_BUILD_BUG +32 lib/test_map_h.c
25
26 #define BUILD_BUG_STREQ(_var, ref) \
27 BUILD_BUG_ON(__builtin_memcmp(_var, ref, __builtin_strlen(ref)))
28 #define BUILD_BUG_STREQ_VI(_vec_, idx, ref) \
29 BUILD_BUG_STREQ(_vec_##_names[idx], ref)
30
31 /* force compile, even if its not called */
> 32 static void MAPH_BUILD_BUG(void)
33 {
34 BUILD_BUG_ON(sum != 6);
35 BUILD_BUG_STREQ(caten, "YESNOMAYBE");
36
37 BUILD_BUG_STREQ_VI(debug_cats, 0, "DRMx_CORE");
38 BUILD_BUG_STREQ_VI(debug_cats, 1, "DRMx_DRIVER");
39 BUILD_BUG_STREQ_VI(debug_cats, 2, "DRMx_KMS");
40
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-08-23 13:52 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=202308232127.6vsYZhdm-lkp@intel.com \
--to=lkp@intel.com \
--cc=jim.cromie@gmail.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.