From: Peter Zijlstra <peterz@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: linux-tip-commits@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Ingo Molnar <mingo@kernel.org>,
x86@kernel.org
Subject: Re: [tip: locking/core] static_call: Fix function type mismatch
Date: Tue, 23 Mar 2021 08:37:33 +0100 [thread overview]
Message-ID: <YFmavWCgUOOfibXR@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <161645580767.398.731817901273202970.tip-bot2@tip-bot2>
On Mon, Mar 22, 2021 at 11:30:07PM -0000, tip-bot2 for Arnd Bergmann wrote:
> The following commit has been merged into the locking/core branch of tip:
>
> Commit-ID: 335c73e7c8f7deb23537afbbbe4f8ab48bd5de52
> Gitweb: https://git.kernel.org/tip/335c73e7c8f7deb23537afbbbe4f8ab48bd5de52
> Author: Arnd Bergmann <arnd@arndb.de>
> AuthorDate: Mon, 22 Mar 2021 22:42:24 +01:00
> Committer: Ingo Molnar <mingo@kernel.org>
> CommitterDate: Tue, 23 Mar 2021 00:08:53 +01:00
>
> static_call: Fix function type mismatch
>
> The __static_call_return0() function is declared to return a 'long',
> while it aliases a couple of functions that all return 'int'. When
> building with 'make W=1', gcc warns about this:
>
> kernel/sched/core.c:5420:37: error: cast between incompatible function types from 'long int (*)(void)' to 'int (*)(void)' [-Werror=cast-function-type]
> 5420 | static_call_update(might_resched, (typeof(&__cond_resched)) __static_call_return0);
>
> Change all these function to return 'long' as well, but remove the cast to
> ensure we get a warning if any of the types ever change.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Signed-off-by: Ingo Molnar <mingo@kernel.org>
> Link: https://lore.kernel.org/r/20210322214309.730556-1-arnd@kernel.org
So I strongly disagree and think the warning is bad and should be
disabled. I'll go uncommit this patch.
next prev parent reply other threads:[~2021-03-23 7:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 21:42 [PATCH] [v2] static_call: fix function type mismatch Arnd Bergmann
2021-03-22 23:30 ` [tip: locking/core] static_call: Fix " tip-bot2 for Arnd Bergmann
2021-03-23 7:37 ` Peter Zijlstra [this message]
2021-03-23 15:49 ` Peter Zijlstra
2021-04-09 11:30 ` [tip: locking/core] static_call: Relax static_call_update() function argument type tip-bot2 for Peter Zijlstra
2021-03-23 7:33 ` [PATCH] [v2] static_call: fix function type mismatch Peter Zijlstra
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=YFmavWCgUOOfibXR@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=x86@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