From: kernel test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [paulmck-rcu:mmap_sem.2023.10.18a 18/31] kernel/locking/qspinlock.c:741:23: warning: no previous declaration for '__pv_spinlock_dump'
Date: Fri, 20 Oct 2023 08:37:08 +0800 [thread overview]
Message-ID: <202310200814.xePmkBus-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git mmap_sem.2023.10.18a
head: 4015256f2bc734d4175381762282784597f41cfa
commit: 851f9c70733ed644c8a03d8f93f9876942181bee [18/31] EXP qspinlock: Add spinlock_dump() to dump lock state
config: x86_64-randconfig-016-20231020 (https://download.01.org/0day-ci/archive/20231020/202310200814.xePmkBus-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231020/202310200814.xePmkBus-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/202310200814.xePmkBus-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/locking/qspinlock.c:741:23: warning: no previous declaration for '__pv_spinlock_dump' [-Wmissing-declarations]
#define spinlock_dump __pv_spinlock_dump
^
kernel/locking/qspinlock.c:691:6: note: in expansion of macro 'spinlock_dump'
void spinlock_dump(spinlock_t *sp, bool full)
^~~~~~~~~~~~~
vim +/__pv_spinlock_dump +741 kernel/locking/qspinlock.c
737
738 #undef queued_spin_lock_slowpath
739 #define queued_spin_lock_slowpath __pv_queued_spin_lock_slowpath
740 #define queued_spin_lock_slowpath_diags __pv_queued_spin_lock_slowpath_diags
> 741 #define spinlock_dump __pv_spinlock_dump
742 #define tail_to_cpu __pv_tail_to_cpu
743 #define tail_to_idx __pv_tail_to_idx
744 #define next_to_prev __pv_next_to_prev
745 #define next_to_cpu_idx __pv_next_to_cpu_idx
746
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-10-20 0:37 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=202310200814.xePmkBus-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paulmck@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).