From: Ammar Faizi <[email protected]>
To: kernel test robot <[email protected]>
Cc: [email protected],
GNU/Weeb Mailing List <[email protected]>
Subject: Re: [ammarfaizi2-block:testing/af/home 3/8] kernel/workqueue.c:4421:5: warning: no previous prototype for 'set_workqueue_cpumask'
Date: Wed, 31 May 2023 12:12:13 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Wed, May 31, 2023 at 09:24:17AM +0800, kernel test robot wrote:
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <[email protected]>
> | Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/
>
> All warnings (new ones prefixed by >>):
>
> >> kernel/workqueue.c:4421:5: warning: no previous prototype for 'set_workqueue_cpumask' [-Wmissing-prototypes]
> 4421 | int set_workqueue_cpumask(struct workqueue_struct *wq, const cpumask_var_t mask)
> | ^~~~~~~~~~~~~~~~~~~~~
I forgot to add the declaration in the header. The fix below:
diff --git a/include/linux/workqueue.h b/include/linux/workqueue.h
index ac551b8ee7d9f2f4..e3bd6f47e74ecd66 100644
--- a/include/linux/workqueue.h
+++ b/include/linux/workqueue.h
@@ -710,6 +710,9 @@ int workqueue_online_cpu(unsigned int cpu);
int workqueue_offline_cpu(unsigned int cpu);
#endif
+int set_workqueue_cpumask(struct workqueue_struct *wq,
+ const cpumask_var_t mask);
+
void __init workqueue_init_early(void);
void __init workqueue_init(void);
--
Ammar Faizi
prev parent reply other threads:[~2023-05-31 5:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 1:24 [ammarfaizi2-block:testing/af/home 3/8] kernel/workqueue.c:4421:5: warning: no previous prototype for 'set_workqueue_cpumask' kernel test robot
2023-05-31 5:12 ` Ammar Faizi [this message]
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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