From: kernel test robot <lkp@intel.com>
To: Jim Cromie <jim.cromie@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jimc:lukas-v3.0 20/24] lib/dynamic_debug.c:621:6: sparse: sparse: symbol 'skip_spaces_and_coma' was not declared. Should it be static?
Date: Thu, 28 Dec 2023 02:50:13 +0800 [thread overview]
Message-ID: <202312280200.lVCy4vxu-lkp@intel.com> (raw)
tree: https://github.com/jimc/linux.git lukas-v3.0
head: 1f42080421213a7819e069d5b6d22cef0b6c9c61
commit: 34cd8a2374f70a56e599ee3e5d786c989d3cb096 [20/24] dyndbg: add skip_spaces_and_coma()
config: i386-randconfig-061-20231227 (https://download.01.org/0day-ci/archive/20231228/202312280200.lVCy4vxu-lkp@intel.com/config)
compiler: ClangBuiltLinux clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231228/202312280200.lVCy4vxu-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/202312280200.lVCy4vxu-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> lib/dynamic_debug.c:621:6: sparse: sparse: symbol 'skip_spaces_and_coma' was not declared. Should it be static?
lib/dynamic_debug.c: note: in included file (through include/linux/mmzone.h, include/linux/gfp.h, include/linux/umh.h, include/linux/kmod.h, ...):
include/linux/page-flags.h:242:46: sparse: sparse: self-comparison always evaluates to false
vim +/skip_spaces_and_coma +621 lib/dynamic_debug.c
620
> 621 char *skip_spaces_and_coma(const char *str)
622 {
623 str = skip_spaces(str);
624 if (*str == ',')
625 str = skip_spaces(++str);
626 return (char *)str;
627 }
628
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-27 18:51 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=202312280200.lVCy4vxu-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.