From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [palmer:intc 5/18] kernel/debug/debug_core.c:420:5: warning: no previous prototype for 'kgdb_has_hit_break'
Date: Fri, 29 May 2020 14:19:38 +0800 [thread overview]
Message-ID: <202005291435.KY0apIfp%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1559 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/palmer/linux.git intc
head: 2bd957e2b0b66894613a189939378cd1c000188d
commit: f83b04d36e52cc3d941120ec859374fcda36eb31 [5/18] kgdb: Add kgdb_has_hit_break function
config: sparc-defconfig (attached as .config)
compiler: sparc-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout f83b04d36e52cc3d941120ec859374fcda36eb31
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=sparc
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>, old ones prefixed by <<):
>> kernel/debug/debug_core.c:420:5: warning: no previous prototype for 'kgdb_has_hit_break' [-Wmissing-prototypes]
420 | int kgdb_has_hit_break(unsigned long addr)
| ^~~~~~~~~~~~~~~~~~
vim +/kgdb_has_hit_break +420 kernel/debug/debug_core.c
419
> 420 int kgdb_has_hit_break(unsigned long addr)
421 {
422 int i;
423
424 for (i = 0; i < KGDB_MAX_BREAKPOINTS; i++) {
425 if (kgdb_break[i].state == BP_ACTIVE &&
426 kgdb_break[i].bpt_addr == addr)
427 return 1;
428 }
429 return 0;
430 }
431
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 13079 bytes --]
reply other threads:[~2020-05-29 6:19 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=202005291435.KY0apIfp%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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.