From: kernel test robot <lkp@intel.com>
To: Jim Cromie <jim.cromie@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jimc:dd-shrink-2e 36/37] lib/dynamic_debug.c:1430:6: warning: no previous prototype for function 'dd_clear_range'
Date: Tue, 3 Oct 2023 16:03:13 +0800 [thread overview]
Message-ID: <202310031624.xCencTRY-lkp@intel.com> (raw)
tree: https://github.com/jimc/linux.git dd-shrink-2e
head: 71a19a8b881bc14025717ba9993f8efcd5e6a44b
commit: 7e48ff541ca0f9ab2496cfbd54976e38ee8910e8 [36/37] dyndbg: add dd_clear_range to prune mtrees
config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20231003/202310031624.xCencTRY-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231003/202310031624.xCencTRY-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/202310031624.xCencTRY-lkp@intel.com/
All warnings (new ones prefixed by >>):
lib/dynamic_debug.c:1408:6: warning: no previous prototype for function 'dd_store_range' [-Wmissing-prototypes]
void dd_store_range(struct maple_tree *mt, const struct _ddebug *start, const struct _ddebug *next,
^
lib/dynamic_debug.c:1408:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
void dd_store_range(struct maple_tree *mt, const struct _ddebug *start, const struct _ddebug *next,
^
static
>> lib/dynamic_debug.c:1430:6: warning: no previous prototype for function 'dd_clear_range' [-Wmissing-prototypes]
void dd_clear_range(const struct _ddebug *start)
^
lib/dynamic_debug.c:1430:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
void dd_clear_range(const struct _ddebug *start)
^
static
2 warnings generated.
vim +/dd_clear_range +1430 lib/dynamic_debug.c
1429
> 1430 void dd_clear_range(const struct _ddebug *start)
1431 {
1432 v3pr_info("clearing %px\n", start);
1433 mtree_erase(&mt_funcs, (unsigned long)start);
1434 mtree_erase(&mt_files, (unsigned long)start);
1435 mtree_erase(&mt_mods, (unsigned long)start);
1436 }
1437
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-10-03 8:04 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=202310031624.xCencTRY-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.