[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20220716044940.45032-1-wangborong@cdjrlc.com>
Date: Sat, 16 Jul 2022 12:49:40 +0800
From: Jason Wang <wangborong@...rlc.com>
To: mingo@...hat.com
Cc: rostedt@...dmis.org, linux-kernel@...r.kernel.org,
Jason Wang <wangborong@...rlc.com>
Subject: [PATCH] tracing/user_events: Fix comment typo
The double `have' is duplicated in the comment, remove one.
Signed-off-by: Jason Wang <wangborong@...rlc.com>
---
kernel/trace/trace_events_user.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/trace/trace_events_user.c b/kernel/trace/trace_events_user.c
index 706e1686b5eb..a6621c52ce45 100644
--- a/kernel/trace/trace_events_user.c
+++ b/kernel/trace/trace_events_user.c
@@ -567,7 +567,7 @@ static int user_event_set_call_visible(struct user_event *user, bool visible)
* to allow user_event files to be less locked down. The extreme case
* being "other" has read/write access to user_events_data/status.
*
- * When not locked down, processes may not have have permissions to
+ * When not locked down, processes may not have permissions to
* add/remove calls themselves to tracefs. We need to temporarily
* switch to root file permission to allow for this scenario.
*/
--
2.35.1
Powered by blists - more mailing lists