From: "tip-bot2 for Haocheng Xie" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Haocheng Xie <xiehaocheng.cn@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: perf/core] perf/hw_breakpoint: Fix DocBook warnings in perf hw_breakpoint
Date: Thu, 27 May 2021 07:38:21 -0000 [thread overview]
Message-ID: <162210110198.29796.2648863634376476070.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20210527031947.1801-4-xiehaocheng.cn@gmail.com>
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 875dd7bf548104bc1d2c5784a6af6cf38215a216
Gitweb: https://git.kernel.org/tip/875dd7bf548104bc1d2c5784a6af6cf38215a216
Author: Haocheng Xie <xiehaocheng.cn@gmail.com>
AuthorDate: Thu, 27 May 2021 11:19:47 +08:00
Committer: Ingo Molnar <mingo@kernel.org>
CommitterDate: Thu, 27 May 2021 09:35:22 +02:00
perf/hw_breakpoint: Fix DocBook warnings in perf hw_breakpoint
Fix the following W=1 kernel build warning(s):
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'
Signed-off-by: Haocheng Xie <xiehaocheng.cn@gmail.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Link: https://lore.kernel.org/r/20210527031947.1801-4-xiehaocheng.cn@gmail.com
---
kernel/events/hw_breakpoint.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/kernel/events/hw_breakpoint.c b/kernel/events/hw_breakpoint.c
index b48d703..8359734 100644
--- a/kernel/events/hw_breakpoint.c
+++ b/kernel/events/hw_breakpoint.c
@@ -451,6 +451,7 @@ int register_perf_hw_breakpoint(struct perf_event *bp)
* register_user_hw_breakpoint - register a hardware breakpoint for user space
* @attr: breakpoint attributes
* @triggered: callback to trigger when we hit the breakpoint
+ * @context: context data could be used in the triggered callback
* @tsk: pointer to 'task_struct' of the process to which the address belongs
*/
struct perf_event *
@@ -550,6 +551,7 @@ EXPORT_SYMBOL_GPL(unregister_hw_breakpoint);
* register_wide_hw_breakpoint - register a wide breakpoint in the kernel
* @attr: breakpoint attributes
* @triggered: callback to trigger when we hit the breakpoint
+ * @context: context data could be used in the triggered callback
*
* @return a set of per_cpu pointers to perf events
*/
prev parent reply other threads:[~2021-05-27 7:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 3:19 [PATCH v2 0/3] perf/events: Fix some build warnings in perf/events subsystem Haocheng Xie
2021-05-27 3:19 ` [PATCH v2 1/3] perf core: Make local function perf_pmu_snapshot_aux() static Haocheng Xie
2021-05-27 7:38 ` [tip: perf/core] perf/core: " tip-bot2 for Haocheng Xie
2021-05-27 3:19 ` [PATCH v2 2/3] perf core: Fix some kernel-doc warnings Haocheng Xie
2021-05-27 7:38 ` [tip: perf/core] perf/core: Fix DocBook warnings tip-bot2 for Haocheng Xie
2021-05-27 3:19 ` [PATCH v2 3/3] perf/hw_breakpoint: Fix kernel-doc warnings in perf hw_breakpoint Haocheng Xie
2021-05-27 7:38 ` tip-bot2 for Haocheng Xie [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=162210110198.29796.2648863634376476070.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=x86@kernel.org \
--cc=xiehaocheng.cn@gmail.com \
/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®