All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ravi Bangoria <ravi.bangoria@amd.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: x86-ml <x86@kernel.org>,
	linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>,
	Ravi Bangoria <ravi.bangoria@amd.com>
Subject: Re: [tip:perf/core] BUILD SUCCESS WITH WARNING e8d7a90c08ce963c592fb49845f2ccc606a2ac21
Date: Thu, 17 Nov 2022 09:26:49 +0530	[thread overview]
Message-ID: <a2feaf02-4b36-f86f-b6ff-018aafe81fac@amd.com> (raw)
In-Reply-To: <Y3VYQtTSJDpwKZR5@hirez.programming.kicks-ass.net>

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

I'll prepare and post a fix.

Thanks,
Ravi

  reply	other threads:[~2022-11-17  3:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16 21:18 [tip:perf/core] BUILD SUCCESS WITH WARNING e8d7a90c08ce963c592fb49845f2ccc606a2ac21 kernel test robot
2022-11-16 21:38 ` Peter Zijlstra
2022-11-17  3:56   ` Ravi Bangoria [this message]
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=a2feaf02-4b36-f86f-b6ff-018aafe81fac@amd.com \
    --to=ravi.bangoria@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.