All of lore.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 V2 0/3] sched: Minor cleanups
Date: Thu, 13 Apr 2017 14:45:47 +0530	[thread overview]
Message-ID: <cover.1492065513.git.viresh.kumar@linaro.org> (raw)

Hi,

Avoid reinitializing memory which is already set to zero.

V1->V2:
- Don't remove field initializers from 2nd and 3rd patch.
- Drop 4th patch (sched: core: drop useless expression from sched_init()).

--
viresh

Viresh Kumar (3):
  sched: topology: drop memset() from init_rootdomain()
  sched: cpudeadline: don't re-initialize struct cpudl
  sched: cpupri: don't re-initialize struct cpupri

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

-- 
2.12.0.432.g71c3a4f4ba37

             reply	other threads:[~2017-04-13  9:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-13  9:15 Viresh Kumar [this message]
2017-04-13  9:15 ` [PATCH V2 1/3] sched: topology: drop memset() from init_rootdomain() Viresh Kumar
2017-08-10 12:05   ` [tip:sched/core] sched/topology: Drop " tip-bot for Viresh Kumar
2017-04-13  9:15 ` [PATCH V2 2/3] sched: cpudeadline: don't re-initialize struct cpudl Viresh Kumar
2017-08-10 12:06   ` [tip:sched/core] sched/deadline: Don't re-initialize 'struct cpudl' tip-bot for Viresh Kumar
2017-04-13  9:15 ` [PATCH V2 3/3] sched: cpupri: don't re-initialize struct cpupri Viresh Kumar
2017-08-10 12:06   ` [tip:sched/core] sched/cpupri: Don't re-initialize 'struct cpupri' tip-bot for 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.1492065513.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.