From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:perf/core] BUILD SUCCESS WITH WARNING e8d7a90c08ce963c592fb49845f2ccc606a2ac21
Date: Thu, 17 Nov 2022 05:18:45 +0800 [thread overview]
Message-ID: <637553b5.ebdZY+lvkXPfAk1E%lkp@intel.com> (raw)
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
elapsed time: 722m
configs tested: 53
configs skipped: 2
gcc tested configs:
arc defconfig
alpha defconfig
s390 defconfig
s390 allmodconfig
arm defconfig
m68k allyesconfig
m68k allmodconfig
x86_64 rhel-8.3-kselftests
arc allyesconfig
x86_64 rhel-8.3-func
ia64 allmodconfig
alpha allyesconfig
i386 defconfig
arm64 allyesconfig
powerpc allnoconfig
i386 randconfig-a012
arm allyesconfig
x86_64 defconfig
x86_64 rhel-8.3-syz
powerpc allmodconfig
i386 randconfig-a014
x86_64 rhel-8.3-kunit
mips allyesconfig
x86_64 randconfig-a013
x86_64 randconfig-a002
x86_64 randconfig-a011
x86_64 rhel-8.3-kvm
i386 allyesconfig
i386 randconfig-a016
sh allmodconfig
x86_64 rhel-8.3
x86_64 randconfig-a015
x86_64 randconfig-a004
x86_64 allyesconfig
x86_64 randconfig-a006
i386 randconfig-a001
i386 randconfig-a003
i386 randconfig-a005
um i386_defconfig
um x86_64_defconfig
s390 allyesconfig
clang tested configs:
i386 randconfig-a013
i386 randconfig-a011
x86_64 randconfig-a001
i386 randconfig-a015
x86_64 randconfig-a012
x86_64 randconfig-a003
x86_64 randconfig-a016
x86_64 randconfig-a005
x86_64 randconfig-a014
i386 randconfig-a002
i386 randconfig-a004
i386 randconfig-a006
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-11-16 21:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 21:18 kernel test robot [this message]
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
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=637553b5.ebdZY+lvkXPfAk1E%lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®