mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Peter Zijlstra <peterz@infradead.org>,
	Linux PM <linux-pm@vger.kernel.org>, Todd Kjos <tkjos@google.com>,
	Joel Fernandes <joelaf@google.com>,
	Colin Cross <ccross@android.com>,
	Ramesh Thomas <ramesh.thomas@intel.com>,
	Alex Shi <alex.shi@linaro.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Mel Gorman <mgorman@suse.de>
Subject: Re: [PATCH RFC] cpuidle/drivers/menu: Remove get_loadavg in the performance multiplier
Date: Wed, 3 Oct 2018 15:05:14 +0200	[thread overview]
Message-ID: <ba6c1dfe-d4ce-c697-3b44-992946cd5c4a@linaro.org> (raw)
In-Reply-To: <CAJZ5v0iRMvhZ1rW40syPRJfYBZ4=zE2-f4HcKaRQsvg18pnTcw@mail.gmail.com>

On 03/10/2018 13:09, Rafael J. Wysocki wrote:
> On Wed, Oct 3, 2018 at 12:25 PM Daniel Lezcano

[ ... ]

> If you send a non-RFC patch to drop get_loadavg() (but you can drop it
> altogether then, there are no other callers of it AFAICS), I'll queue
> it up after the 4.20 (or whatever it turns out to be in the end) merge
> window so all of the CIs out there have a chance to report issues (if
> any).

Sure, I can do that. There were some changes in this file, shall I base
the patch on v4.19-rc6 or linux-pm/linux-next ?


-- 
 <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog


      reply	other threads:[~2018-10-03 13:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-25  9:38 Daniel Lezcano
2018-10-03  8:58 ` Rafael J. Wysocki
2018-10-03 10:25   ` Daniel Lezcano
2018-10-03 11:09     ` Rafael J. Wysocki
2018-10-03 13:05       ` Daniel Lezcano [this message]

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=ba6c1dfe-d4ce-c697-3b44-992946cd5c4a@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=alex.shi@linaro.org \
    --cc=ccross@android.com \
    --cc=joelaf@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=peterz@infradead.org \
    --cc=rafael@kernel.org \
    --cc=ramesh.thomas@intel.com \
    --cc=rjw@rjwysocki.net \
    --cc=tkjos@google.com \
    /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

all inboxes | Powered by JetHome®