mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
To: linux-kernel@vger.kernel.org
Cc: rostedt@goodmis.org, fweisbec@gmail.com, mingo@redhat.com,
	Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
Subject: [PATCH 0/3 for-tip] use task_nice() in tracing to git rid of an open coded impolementation of it.
Date: Wed, 12 Mar 2014 18:26:41 +0800	[thread overview]
Message-ID: <cover.1394619587.git.yangds.fnst@cn.fujitsu.com> (raw)

Hi Steven,
	The [1/3] in this thread is a copy of 

1390430505-17234-1-git-send-email-yangds.fnst@cn.fujitsu.com.

	At that time, you said you will take this patch if task_nice()
is implemeted as a inline function. Now it is done, I wish you can give
it an ack. If you have a time, please take a look at the other patches
in this thread. Thank you.

Dongsheng Yang (3):
  tracing: Use inline task_nice() to get rid of an open coded
    implementation of it.
  sched/prio: Replace hardcoding of 40 with NICE_WIDTH.
  sched: Use clamp() and clamp_val() to make it more readable.

 kernel/sched/core.c  | 11 ++---------
 kernel/trace/trace.c |  2 +-
 2 files changed, 3 insertions(+), 10 deletions(-)

-- 
1.8.2.1


             reply	other threads:[~2014-03-12 10:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-12 10:26 Dongsheng Yang [this message]
2014-03-12 10:26 ` [PATCH 1/3 Resend] tracing: Use inline task_nice() to get rid of an open coded implementation " Dongsheng Yang
2014-03-19  2:15   ` Steven Rostedt
2014-03-19  2:20     ` Dongsheng Yang
2014-05-08  6:38     ` [PATCH RESEND] " Dongsheng Yang
2014-05-09  0:17       ` Dongsheng Yang
2014-05-09  1:23         ` Steven Rostedt
2014-03-12 10:26 ` [PATCH 2/3] sched/prio: Replace hardcoding of 40 with NICE_WIDTH Dongsheng Yang
2014-03-12 10:26 ` [PATCH 3/3] sched: Use clamp() and clamp_val() to make it more readable Dongsheng Yang
2014-03-19  2:16   ` Steven Rostedt
2014-03-19  2:19     ` Dongsheng Yang

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=cover.1394619587.git.yangds.fnst@cn.fujitsu.com \
    --to=yangds.fnst@cn.fujitsu.com \
    --cc=fweisbec@gmail.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

Powered by JetHome