linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ed Tsai <ed.tsai@mediatek.com>
To: <rostedt@goodmis.org>, <mingo@redhat.com>,
	<linux-kernel@vger.kernel.org>
Cc: Ed Tsai <ed.tsai@mediatek.com>
Subject: [PATCH 1/1] sched: remove the redundant 'success' in the sched tracepoint
Date: Thu, 22 Apr 2021 20:22:26 +0800	[thread overview]
Message-ID: <20210422122226.9415-1-ed.tsai@mediatek.com> (raw)

'success' is left here for a long time and also it is meaningless
for the upper user. Just remove it.

Signed-off-by: Ed Tsai <ed.tsai@mediatek.com>
---
 include/trace/events/sched.h | 2 --
 1 file changed, 2 deletions(-)

diff --git a/include/trace/events/sched.h b/include/trace/events/sched.h
index cbe3e152d24c..720204539e0b 100644
--- a/include/trace/events/sched.h
+++ b/include/trace/events/sched.h
@@ -148,7 +148,6 @@ DECLARE_EVENT_CLASS(sched_wakeup_template,
 		__array(	char,	comm,	TASK_COMM_LEN	)
 		__field(	pid_t,	pid			)
 		__field(	int,	prio			)
-		__field(	int,	success			)
 		__field(	int,	target_cpu		)
 	),
 
@@ -156,7 +155,6 @@ DECLARE_EVENT_CLASS(sched_wakeup_template,
 		memcpy(__entry->comm, p->comm, TASK_COMM_LEN);
 		__entry->pid		= p->pid;
 		__entry->prio		= p->prio; /* XXX SCHED_DEADLINE */
-		__entry->success	= 1; /* rudiment, kill when possible */
 		__entry->target_cpu	= task_cpu(p);
 	),
 
-- 
2.18.0


             reply	other threads:[~2021-04-22 12:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22 12:22 Ed Tsai [this message]
2021-04-22 15:46 ` [PATCH 1/1] sched: remove the redundant 'success' in the sched tracepoint Steven Rostedt
2021-04-23  0:38   ` Ed Tsai
2021-04-25 21:54     ` Steven Rostedt
2021-04-26  6:18       ` Ed Tsai
2021-04-26 13:48         ` Steven Rostedt
2021-04-26  8:09       ` Peter Zijlstra

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=20210422122226.9415-1-ed.tsai@mediatek.com \
    --to=ed.tsai@mediatek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.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).