From: Valentin Schneider <vschneid@redhat.com>
To: Tejun Heo <tj@kernel.org>, Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the workqueues tree
Date: Fri, 13 Jan 2023 16:47:31 +0000 [thread overview]
Message-ID: <xhsmhzgamidp8.mognet@vschneid.remote.csb> (raw)
In-Reply-To: <Y8GHXUcXYJcHPkOY@slm.duckdns.org>
On 13/01/23 06:31, Tejun Heo wrote:
> On Fri, Jan 13, 2023 at 02:31:02PM +1100, Stephen Rothwell wrote:
>> Hi all,
>>
>> After merging the workqueues tree, today's linux-next build (x86_64
>> allnoconfig and several others) produced this warning:
>>
>> kernel/workqueue.c:1993:13: warning: 'rebind_worker' defined but not used [-Wunused-function]
>> 1993 | static void rebind_worker(struct worker *worker, struct worker_pool *pool)
>> | ^~~~~~~~~~~~~
>>
>> Introduced by commit
>>
>> 793777bc193b ("workqueue: Factorize unbind/rebind_workers() logic")
>
> Valentin, this is caused by rebind_worker() being only used by
> rebind_workers() which is inside CONFIG_SMP. I don't see any other uses of
> rebind_worker(). Just fold it back into rebind_workers()?
>
Woops! Yes I only did it to keep things aligned with unbind_workers(), let
me resend with that folded back in. Sorry!
> Thanks.
>
> --
> tejun
next prev parent reply other threads:[~2023-01-13 16:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 3:31 linux-next: build warning after merge of the workqueues tree Stephen Rothwell
2023-01-13 16:31 ` Tejun Heo
2023-01-13 16:47 ` Valentin Schneider [this message]
2023-01-13 16:48 ` Valentin Schneider
2023-01-13 17:16 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2024-08-21 3:45 Stephen Rothwell
2024-08-14 4:18 Stephen Rothwell
2024-02-16 3:00 Stephen Rothwell
2024-02-16 4:46 ` Tejun Heo
2024-02-09 3:24 Stephen Rothwell
2024-02-09 3:45 ` Waiman Long
2024-01-30 2:37 Stephen Rothwell
2024-04-21 23:48 ` Stephen Rothwell
2024-04-22 19:59 ` Tejun Heo
2024-04-22 20:13 ` Tejun Heo
2013-03-19 3:58 Stephen Rothwell
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=xhsmhzgamidp8.mognet@vschneid.remote.csb \
--to=vschneid@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tj@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