From: Peter Zijlstra <peterz@infradead.org>
To: Ravi Bangoria <ravi.bangoria@amd.com>
Cc: x86-ml <x86@kernel.org>,
linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [tip:perf/core] BUILD SUCCESS WITH WARNING e8d7a90c08ce963c592fb49845f2ccc606a2ac21
Date: Thu, 17 Nov 2022 09:18:16 +0100 [thread overview]
Message-ID: <Y3XuSNJseSRckyHn@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <a2feaf02-4b36-f86f-b6ff-018aafe81fac@amd.com>
On Thu, Nov 17, 2022 at 09:26:49AM +0530, Ravi Bangoria wrote:
> Hi Peter,
>
> >> kernel/events/core.c:11274:4: warning: cast from 'int (*)(struct perf_cpu_pmu_context *)' to 'remote_function_f' (aka 'int (*)(void *)') converts to incompatible function type [-Wcast-function-type-strict]
> >>
> >> Warning ids grouped by kconfigs:
> >>
> >> clang_recent_errors
> >> |-- hexagon-randconfig-r001-20221116
> >> | `-- kernel-events-core.c:warning:cast-from-int-(-)(struct-perf_cpu_pmu_context-)-to-remote_function_f-(aka-int-(-)(void-)-)-converts-to-incompatible-function-type
> >> |-- hexagon-randconfig-r005-20221116
> >> | `-- kernel-events-core.c:warning:cast-from-int-(-)(struct-perf_cpu_pmu_context-)-to-remote_function_f-(aka-int-(-)(void-)-)-converts-to-incompatible-function-type
> >> `-- s390-randconfig-r012-20221116
> >> `-- kernel-events-core.c:warning:cast-from-int-(-)(struct-perf_cpu_pmu_context-)-to-remote_function_f-(aka-int-(-)(void-)-)-converts-to-incompatible-function-type
> >
> > Robot guys; why don't I have a report of this warning?
>
> https://lore.kernel.org/all/202211041643.J58xvn1k-lkp@intel.com
Hurgh, clearly I can't even search :/
> I'll prepare and post a fix.
Already did that last night:
https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git/commit/?h=perf/core&id=3aed27110419792e8e26ba3aed1dd9462975cc6e
next prev parent reply other threads:[~2022-11-17 8:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 21:18 kernel test robot
2022-11-16 21:38 ` Peter Zijlstra
2022-11-17 3:56 ` Ravi Bangoria
2022-11-17 8:18 ` Peter Zijlstra [this message]
2022-11-17 10:26 ` Chen, Rong A
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=Y3XuSNJseSRckyHn@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ravi.bangoria@amd.com \
--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
all inboxes | Powered by JetHome®