From: Martin von Gagern <Martin.vGagern@gmx.net>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: cpufreq@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: ignore_nice vs. ignore_nice_load
Date: Tue, 06 Aug 2013 09:40:13 +0200 [thread overview]
Message-ID: <5200A85D.8000602@gmx.net> (raw)
In-Reply-To: <CAOh2x=kriqCRp9x+f5f5onDVoyfxVHSPDF5HrM_sFSsQ1ucktw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 202 bytes --]
On 05.08.2013 09:01, Viresh Kumar wrote:
> Please try following patch (attached for applying).
> [0001-cpufreq-rename-ignore_nice-as-ignore_nice_load.patch]
Looks good here.
Thanks,
Martin
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2013-08-06 7:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51FC1935.5030702@gmx.net>
2013-08-05 7:01 ` ignore_nice vs. ignore_nice_load Viresh Kumar
2013-08-05 13:00 ` Rafael J. Wysocki
2013-08-06 7:40 ` Martin von Gagern [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=5200A85D.8000602@gmx.net \
--to=martin.vgagern@gmx.net \
--cc=cpufreq@vger.kernel.org \
--cc=linux-pm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).