All of lore.kernel.org
 help / color / mirror / Atom feed
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 3/3] perf/hw_breakpoint: Fix kernel-doc warnings in perf hw_breakpoint
Date: Thu, 27 May 2021 11:19:47 +0800	[thread overview]
Message-ID: <20210527031947.1801-4-xiehaocheng.cn@gmail.com> (raw)
In-Reply-To: <20210527031947.1801-1-xiehaocheng.cn@gmail.com>

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>
---
 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
  */
-- 
2.9.5


  parent reply	other threads:[~2021-05-27  3:20 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 ` Haocheng Xie [this message]
2021-05-27  7:38   ` [tip: perf/core] perf/hw_breakpoint: Fix DocBook warnings in perf hw_breakpoint tip-bot2 for 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-4-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 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.