All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leo Yan <leo.yan@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
	Vikram Mulukutla <markivx@codeaurora.org>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>
Subject: Re: [PATCH] sched/cpufreq: Remove unused macro SUGOV_KTHREAD_PRIORITY
Date: Thu, 8 Feb 2018 23:23:30 +0800	[thread overview]
Message-ID: <20180208152330.GA16412@leoy-ThinkPad-X240s> (raw)
In-Reply-To: <CAOh2x==puw3JaGYFGRN4y7ZGxmb7iHf6BDUif8c+utzvz1uXLA@mail.gmail.com>

On Thu, Feb 08, 2018 at 07:34:54PM +0530, Viresh Kumar wrote:
> Forgot Cc'ing me ? :)

I meant to copy you, but I wrongly added Vikram :)

> On Thu, Feb 8, 2018 at 7:18 PM, Leo Yan <leo.yan@linaro.org> wrote:
> > Since schedutil kernel thread directly set priority to 0, the macro
> > SUGOV_KTHREAD_PRIORITY is not used.  So remove it.
> >
> > Cc: Vikram Mulukutla <markivx@codeaurora.org>
> > Cc: Vincent Guittot <vincent.guittot@linaro.org>
> > Cc: Daniel Lezcano <daniel.lezcano@linaro.org>
> > Signed-off-by: Leo Yan <leo.yan@linaro.org>
> > ---
> >  kernel/sched/cpufreq_schedutil.c | 2 --
> >  1 file changed, 2 deletions(-)
> 
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>

Thanks for acking, Viresh and Daniel.

  reply	other threads:[~2018-02-08 15:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-08 13:48 [PATCH] sched/cpufreq: Remove unused macro SUGOV_KTHREAD_PRIORITY Leo Yan
2018-02-08 14:04 ` Viresh Kumar
2018-02-08 15:23   ` Leo Yan [this message]
2018-02-08 14:06 ` Daniel Lezcano
2018-02-13 12:15 ` [tip:sched/urgent] sched/cpufreq: Remove unused SUGOV_KTHREAD_PRIORITY macro tip-bot for Leo Yan

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=20180208152330.GA16412@leoy-ThinkPad-X240s \
    --to=leo.yan@linaro.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markivx@codeaurora.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=vincent.guittot@linaro.org \
    --cc=viresh.kumar@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.