public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Ingo Molnar <mingo@redhat.com>, Peter Zijlstra <peterz@infradead.org>
Cc: linaro-kernel@lists.linaro.org, linux-kernel@vger.kernel.org,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH 0/4] sched: Minor cleanups
Date: Thu, 23 Mar 2017 17:05:55 +0530	[thread overview]
Message-ID: <cover.1490268634.git.viresh.kumar@linaro.org> (raw)

Hi,

Here are few minor cleanups for the sched core. The first three tries to
avoid reinitializing memory which is already set to zero and the last
one drops an unused statement.

--
viresh

Viresh Kumar (4):
  sched: topology: drop memset() from init_rootdomain()
  sched: cpudeadline: don't re-initialize struct cpudl
  sched: cpupri: don't re-initialize struct cpupri
  sched: core: drop useless expression from sched_init()

 kernel/sched/core.c        | 1 -
 kernel/sched/cpudeadline.c | 2 --
 kernel/sched/cpupri.c      | 3 ---
 kernel/sched/topology.c    | 4 +---
 4 files changed, 1 insertion(+), 9 deletions(-)

-- 
2.12.0.432.g71c3a4f4ba37

             reply	other threads:[~2017-03-23 11:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23 11:35 Viresh Kumar [this message]
2017-03-23 11:35 ` [PATCH 1/4] sched: topology: drop memset() from init_rootdomain() Viresh Kumar
2017-03-23 11:35 ` [PATCH 2/4] sched: cpudeadline: don't re-initialize struct cpudl Viresh Kumar
2017-03-23 11:35 ` [PATCH 3/4] sched: cpupri: don't re-initialize struct cpupri Viresh Kumar
2017-03-23 11:35 ` [PATCH 4/4] sched: core: drop useless expression from sched_init() Viresh Kumar
2017-03-27 13:58 ` [PATCH 0/4] sched: Minor cleanups Peter Zijlstra
2017-04-10  9:30   ` Viresh Kumar

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.1490268634.git.viresh.kumar@linaro.org \
    --to=viresh.kumar@linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=vincent.guittot@linaro.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