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.