From: kernel test robot <lkp@intel.com>
To: Jim Cromie <jim.cromie@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jimc:dd-drm-fix-next 15/19] lib/test_map_h.c:21:1: sparse: sparse: symbol 'debug_cats_slist' was not declared. Should it be static?
Date: Mon, 20 Mar 2023 00:49:22 +0800 [thread overview]
Message-ID: <202303200005.vo8oC4w2-lkp@intel.com> (raw)
tree: https://github.com/jimc/linux.git dd-drm-fix-next
head: c4b31485bf709f2667d85485ee94f8bc2f7c91d1
commit: fdaf7cf52761c58abe98dc278e4e4b12785a0e6c [15/19] dyndbg: add map.h, test_map_h.c (RFC)
config: i386-randconfig-s002 (https://download.01.org/0day-ci/archive/20230320/202303200005.vo8oC4w2-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-39-gce1a6720-dirty
# https://github.com/jimc/linux/commit/fdaf7cf52761c58abe98dc278e4e4b12785a0e6c
git remote add jimc https://github.com/jimc/linux.git
git fetch --no-tags jimc dd-drm-fix-next
git checkout fdaf7cf52761c58abe98dc278e4e4b12785a0e6c
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 olddefconfig
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202303200005.vo8oC4w2-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> lib/test_map_h.c:21:1: sparse: sparse: symbol 'debug_cats_slist' was not declared. Should it be static?
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-03-19 16:50 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=202303200005.vo8oC4w2-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.