From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android16-6.12 0/1] fs/fs-writeback.c:138:6: warning: no previous prototype for 'wb_wakeup'
Date: Thu, 02 Jul 2026 11:18:18 +0800 [thread overview]
Message-ID: <202607021123.hgAEHA4i-lkp@intel.com> (raw)
Hi Bo,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android16-6.12
head: 030ed2af4ba8ba50d5f3cbbc704bc93df568d84e
commit: 55cf94258af72fd493779ab2b7a4278d5c8d1d21 [0/1] ANDROID: writeback: export symbols to do a hierarchical writeback control
config: x86_64-randconfig-006-20260702 (https://download.01.org/0day-ci/archive/20260702/202607021123.hgAEHA4i-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260702/202607021123.hgAEHA4i-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/202607021123.hgAEHA4i-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/fs-writeback.c:138:6: warning: no previous prototype for 'wb_wakeup' [-Wmissing-prototypes]
138 | void wb_wakeup(struct bdi_writeback *wb)
| ^~~~~~~~~
>> fs/fs-writeback.c:1349:6: warning: no previous prototype for 'redirty_tail_locked' [-Wmissing-prototypes]
1349 | void redirty_tail_locked(struct inode *inode, struct bdi_writeback *wb)
| ^~~~~~~~~~~~~~~~~~~
vim +/wb_wakeup +138 fs/fs-writeback.c
137
> 138 void wb_wakeup(struct bdi_writeback *wb)
139 {
140 spin_lock_irq(&wb->work_lock);
141 if (test_bit(WB_registered, &wb->state))
142 mod_delayed_work(bdi_wq, &wb->dwork, 0);
143 spin_unlock_irq(&wb->work_lock);
144 }
145 EXPORT_SYMBOL_GPL(wb_wakeup);
146
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-02 3: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=202607021123.hgAEHA4i-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.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.