[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220714164328.093858818@goodmis.org>
Date: Thu, 14 Jul 2022 12:42:57 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: linux-kernel@...r.kernel.org
Cc: Ingo Molnar <mingo@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Xiang wangx <wangxiang@...rlc.com>
Subject: [for-next][PATCH 01/23] tracing/user_events: Fix syntax errors in comments
From: Xiang wangx <wangxiang@...rlc.com>
Delete the redundant word 'have'.
Link: https://lkml.kernel.org/r/20220606023007.23377-1-wangxiang@cdjrlc.com
Signed-off-by: Xiang wangx <wangxiang@...rlc.com>
Signed-off-by: Steven Rostedt (Google) <rostedt@...dmis.org>
---
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