From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: rjw@rjwysocki.net
Cc: linux-pm@vger.kernel.org,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: [PATCH 0/2] PID debugfs files
Date: Thu, 20 Oct 2016 13:37:04 -0700 [thread overview]
Message-ID: <1476995826-15536-1-git-send-email-srinivas.pandruvada@linux.intel.com> (raw)
When PID is not used don't present PID parameters to tune.
Also update documentation.
Srinivas Pandruvada (2):
cpufreq: intel_pstate: Remove PID debugfs when not used
Documentation: intel_pstate: PID tuning is not always available
Documentation/cpu-freq/intel-pstate.txt | 9 +++++----
drivers/cpufreq/intel_pstate.c | 4 +++-
2 files changed, 8 insertions(+), 5 deletions(-)
--
2.7.4
next reply other threads:[~2016-10-20 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 20:37 Srinivas Pandruvada [this message]
2016-10-20 20:37 ` [PATCH 1/2] cpufreq: intel_pstate: Remove PID debugfs when not used Srinivas Pandruvada
2016-10-20 20:37 ` [PATCH 2/2] Documentation: intel_pstate: PID tuning is not always available Srinivas Pandruvada
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=1476995826-15536-1-git-send-email-srinivas.pandruvada@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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).