From: kernel test robot <lkp@intel.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [koverstreet-bcachefs:bcachefs-debug 231/231] fs/bcachefs/btree/locking.c:957:6: warning: no previous prototype for 'bch2_account_sched_blocked'
Date: Tue, 20 Jan 2026 18:38:58 +0800 [thread overview]
Message-ID: <202601201853.pbX2xazZ-lkp@intel.com> (raw)
tree: https://github.com/koverstreet/bcachefs bcachefs-debug
head: 7cd4e8f9f8f13d9c5a2bbc98b80ca164430d6062
commit: 7cd4e8f9f8f13d9c5a2bbc98b80ca164430d6062 [231/231] BCH_SB_COUNTER_blocked_with_btree_locks_held
config: sh-allmodconfig (https://download.01.org/0day-ci/archive/20260120/202601201853.pbX2xazZ-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260120/202601201853.pbX2xazZ-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/202601201853.pbX2xazZ-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/bcachefs/btree/locking.c:957:6: warning: no previous prototype for 'bch2_account_sched_blocked' [-Wmissing-prototypes]
957 | void bch2_account_sched_blocked(u64 start_time)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/bch2_account_sched_blocked +957 fs/bcachefs/btree/locking.c
956
> 957 void bch2_account_sched_blocked(u64 start_time)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-01-20 10:39 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=202601201853.pbX2xazZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=kent.overstreet@linux.dev \
--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.