All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jim Cromie <jim.cromie@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jimc:maph 7/7] lib/test_map_h.c:32:13: warning: 'MAPH_BUILD_BUG' defined but not used
Date: Mon, 21 Aug 2023 17:13:11 +0800	[thread overview]
Message-ID: <202308211744.grp4p8kb-lkp@intel.com> (raw)

Hi Jim,

First bad commit (maybe != root cause):

tree:   https://github.com/jimc/linux.git maph
head:   7f5a5e57c1ce6971acdfa13d3e177b14fe615838
commit: 7f5a5e57c1ce6971acdfa13d3e177b14fe615838 [7/7] drop-DD-CORE-dep
config: m68k-defconfig (https://download.01.org/0day-ci/archive/20230821/202308211744.grp4p8kb-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230821/202308211744.grp4p8kb-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/202308211744.grp4p8kb-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

8bf2d83c02781d Jim Cromie 2023-03-25  25  
8bf2d83c02781d Jim Cromie 2023-03-25  26  #define BUILD_BUG_STREQ(_var, ref)					\
8bf2d83c02781d Jim Cromie 2023-03-25  27  	BUILD_BUG_ON(__builtin_memcmp(_var, ref, __builtin_strlen(ref)))
8bf2d83c02781d Jim Cromie 2023-03-25  28  #define BUILD_BUG_STREQ_VI(_vec_, idx, ref)		\
8bf2d83c02781d Jim Cromie 2023-03-25  29  	BUILD_BUG_STREQ(_vec_##_names[idx], ref)
8bf2d83c02781d Jim Cromie 2023-03-25  30  
8bf2d83c02781d Jim Cromie 2023-03-25  31  /* force compile, even if its not called */
3acf936f65d59e Jim Cromie 2023-04-25 @32  static void MAPH_BUILD_BUG(void)
8bf2d83c02781d Jim Cromie 2023-03-25  33  {
8bf2d83c02781d Jim Cromie 2023-03-25  34  	BUILD_BUG_ON(sum != 6);
8bf2d83c02781d Jim Cromie 2023-03-25  35  	BUILD_BUG_STREQ(caten, "YESNOMAYBE");
8bf2d83c02781d Jim Cromie 2023-03-25  36  
8bf2d83c02781d Jim Cromie 2023-03-25  37  	BUILD_BUG_STREQ_VI(debug_cats, 0, "DRMx_CORE");
8bf2d83c02781d Jim Cromie 2023-03-25  38  	BUILD_BUG_STREQ_VI(debug_cats, 1, "DRMx_DRIVER");
8bf2d83c02781d Jim Cromie 2023-03-25  39  	BUILD_BUG_STREQ_VI(debug_cats, 2, "DRMx_KMS");
8bf2d83c02781d Jim Cromie 2023-03-25  40  

:::::: The code at line 32 was first introduced by commit
:::::: 3acf936f65d59ef4588b1c10924acc77c157b205 strip-used-MAPH-BB

:::::: TO: Jim Cromie <jim.cromie@gmail.com>
:::::: CC: Jim Cromie <jim.cromie@gmail.com>

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

                 reply	other threads:[~2023-08-21  9:15 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=202308211744.grp4p8kb-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.