From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Peter Zijlstra <peterz@infradead.org>, kernel test robot <lkp@intel.com>
Cc: x86-ml <x86@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [tip:perf/core] BUILD SUCCESS WITH WARNING e8d7a90c08ce963c592fb49845f2ccc606a2ac21
Date: Thu, 17 Nov 2022 18:26:27 +0800 [thread overview]
Message-ID: <ef7e121e-5424-36b3-6cb2-a80cece7290c@intel.com> (raw)
In-Reply-To: <Y3VYQtTSJDpwKZR5@hirez.programming.kicks-ass.net>
On 11/17/2022 5:38 AM, Peter Zijlstra wrote:
> On Thu, Nov 17, 2022 at 05:18:45AM +0800, kernel test robot wrote:
>> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf/core
>> branch HEAD: e8d7a90c08ce963c592fb49845f2ccc606a2ac21 perf: Fix possible memleak in pmu_dev_alloc()
>>
>> Warning: (recently discovered and may have been fixed)
>>
>> 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?
>
> Also, this very much isn't caused by this patch, this is a pre-existing
> issue.
>
Hi Peter,
Sorry for the misunderstanding,it's a summary report to show recent
issues, we didn't find it in your repo before merging into tip tree,
we'll take a look to improve the system.
Best Regards,
Rong Chen
prev parent reply other threads:[~2022-11-17 10:26 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
2022-11-17 10:26 ` Chen, Rong A [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 \
--in-reply-to=ef7e121e-5424-36b3-6cb2-a80cece7290c@intel.com \
--to=rong.a.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®