From: Haocheng Xie <xiehaocheng.cn@gmail.com>
To: mingo@kernel.org, acme@kernel.org,
alexander.shishkin@linux.intel.com, jolsa@redhat.com,
mark.rutland@arm.com, mingo@redhat.com, namhyung@kernel.org,
peterz@infradead.org
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Haocheng Xie <xiehaocheng.cn@gmail.com>
Subject: [PATCH v2 0/3] perf/events: Fix some build warnings in perf/events subsystem.
Date: Thu, 27 May 2021 11:19:44 +0800 [thread overview]
Message-ID: <20210527031947.1801-1-xiehaocheng.cn@gmail.com> (raw)
I have got these warnings when building kernel with 'W=1' options:
kernel/events/core.c:6670:6: warning: no previous prototype for 'perf_pmu_snapshot_aux' [-Wmissing-prototypes]
kernel/events/core.c:143: warning: Function parameter or member 'cpu' not described in 'cpu_function_call'
kernel/events/core.c:11924: warning: Function parameter or member 'flags' not described in 'sys_perf_event_open'
kernel/events/core.c:12382: warning: Function parameter or member 'overflow_handler' not described in 'perf_event_create_kernel_counter'
kernel/events/core.c:12382: warning: Function parameter or member 'context' not described in 'perf_event_create_kernel_counter'
kernel/events/hw_breakpoint.c:461: warning: Function parameter or member 'context' not described in 'register_user_hw_breakpoint'
kernel/events/hw_breakpoint.c:560: warning: Function parameter or member 'context' not described in 'register_wide_hw_breakpoint'
The 3-patch series will fix these warnings.
Changes from v1:
- optimize the commit message format.
- remove superfluous whitespace in the subject.
- align the arguments of modified function.
Haocheng Xie (3):
perf core: Make local function perf_pmu_snapshot_aux() static
perf core: Fix some kernel-doc warnings.
perf/hw_breakpoint: Fix kernel-doc warnings in perf hw_breakpoint
kernel/events/core.c | 12 ++++++++----
kernel/events/hw_breakpoint.c | 2 ++
2 files changed, 10 insertions(+), 4 deletions(-)
--
2.9.5
next reply other threads:[~2021-05-27 3:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 3:19 Haocheng Xie [this message]
2021-05-27 3:19 ` [PATCH v2 1/3] perf core: Make local function perf_pmu_snapshot_aux() static Haocheng Xie
2021-05-27 3:19 ` [PATCH v2 2/3] perf core: Fix some kernel-doc warnings Haocheng Xie
2021-05-27 3:19 ` [PATCH v2 3/3] perf/hw_breakpoint: Fix kernel-doc warnings in perf hw_breakpoint Haocheng Xie
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=20210527031947.1801-1-xiehaocheng.cn@gmail.com \
--to=xiehaocheng.cn@gmail.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).