From: kernel test robot <lkp@intel.com>
To: Johannes Berg <johannes.berg@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 3857/4552] htmldocs: ./include/net/cfg80211.h:5891: warning: expecting prototype for wiphy_delayed work_flush(). Prototype was for wiphy_delayed_work_flush() instead
Date: Wed, 13 Sep 2023 08:08:46 +0800 [thread overview]
Message-ID: <202309130803.vjwpbJWy-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 3c13c772fc233a10342c8e1605ff0855dfdf0c89
commit: 56cfb8ce1f7f6c4e5ca571a2ec0880e131cd0311 [3857/4552] wifi: cfg80211: add flush functions for wiphy work
reproduce: (https://download.01.org/0day-ci/archive/20230913/202309130803.vjwpbJWy-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/202309130803.vjwpbJWy-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> ./include/net/cfg80211.h:5891: warning: expecting prototype for wiphy_delayed work_flush(). Prototype was for wiphy_delayed_work_flush() instead
vim +5891 ./include/net/cfg80211.h
5853
5854 /**
5855 * wiphy_delayed_work_queue - queue delayed work for the wiphy
5856 * @wiphy: the wiphy to queue for
5857 * @dwork: the delayable worker
5858 * @delay: number of jiffies to wait before queueing
5859 *
5860 * This is useful for work that must be done asynchronously, and work
5861 * queued here has the special property that the wiphy mutex will be
5862 * held as if wiphy_lock() was called, and that it cannot be running
5863 * after wiphy_lock() was called. Therefore, wiphy_cancel_work() can
5864 * use just cancel_work() instead of cancel_work_sync(), it requires
5865 * being in a section protected by wiphy_lock().
5866 */
5867 void wiphy_delayed_work_queue(struct wiphy *wiphy,
5868 struct wiphy_delayed_work *dwork,
5869 unsigned long delay);
5870
5871 /**
5872 * wiphy_delayed_work_cancel - cancel previously queued delayed work
5873 * @wiphy: the wiphy, for debug purposes
5874 * @dwork: the delayed work to cancel
5875 *
5876 * Cancel the work *without* waiting for it, this assumes being
5877 * called under the wiphy mutex acquired by wiphy_lock().
5878 */
5879 void wiphy_delayed_work_cancel(struct wiphy *wiphy,
5880 struct wiphy_delayed_work *dwork);
5881
5882 /**
5883 * wiphy_delayed work_flush - flush previously queued delayed work
5884 * @wiphy: the wiphy, for debug purposes
5885 * @work: the work to flush
5886 *
5887 * Flush the work (i.e. run it if pending). This must be called
5888 * under the wiphy mutex acquired by wiphy_lock().
5889 */
5890 void wiphy_delayed_work_flush(struct wiphy *wiphy,
> 5891 struct wiphy_delayed_work *dwork);
5892
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-09-13 0:09 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=202309130803.vjwpbJWy-lkp@intel.com \
--to=lkp@intel.com \
--cc=johannes.berg@intel.com \
--cc=linux-mm@kvack.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox