linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux PM <linux-pm@vger.kernel.org>, Jonathan Corbet <corbet@lwn.net>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Doug Smythies <dsmythies@telus.net>
Subject: Re: [Update][PATCH v2 5/5] cpufreq: intel_pstate: Document the current behavior and user interface
Date: Tue, 18 Apr 2017 16:24:59 +0200	[thread overview]
Message-ID: <1603932.3tl1vUv8H6@aspire.rjw.lan> (raw)
In-Reply-To: <4096353.uPKQmKGfWK@aspire.rjw.lan>

Hi Jon,

On Thursday, March 30, 2017 11:01:48 PM Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> 
> Add a document describing the current behavior and user space
> interface of the intel_pstate driver in the RST format and
> drop the existing outdated intel_pstate.txt document.
> 
> Also update admin-guide/pm/cpufreq.rst with proper RST references
> to the new intel_pstate.rst document.
> 
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> ---
> 
> -> v2:
> Mention the previously requested target P-state in the description of the
> "Core" variant of active mode "powersave" algorithm and drop the example
> part of the "Tuning Interface in ``debugfs``" section which was off-base by
> a wide margin (thanks to Doug for pointing out these issues to me).

This was posted some time ago and all of the functionality described by it has
been in linux-next for quite a while, so I'm wondering if it's possible to
route it through the documentation tree as it epends on 
Documentation/admin-guide/pm/cpufreq.rst already in there?

I can resend it afresh if that helps.

Thanks,
Rafael

  reply	other threads:[~2017-04-18 14:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-22 22:50 [PATCH 0/5] cpufreq: intel_pstate: HW support changes, limits rework and documentation Rafael J. Wysocki
2017-03-22 22:52 ` [PATCH 1/5] cpufreq: intel_pstate: Support HWP processors in all operation modes Rafael J. Wysocki
2017-03-22 22:53 ` [PATCH 2/5] cpufreq: intel_pstate: Use load-based P-state selection more widely Rafael J. Wysocki
2017-03-22 22:58 ` [PATCH 3/5] cpufreq: intel_pstate: Active mode P-state limits rework Rafael J. Wysocki
2017-03-22 23:00 ` [PATCH 4/5] cpufreq: intel_pstate: Avoid transient updates of cpuinfo.max_freq Rafael J. Wysocki
2017-03-22 23:32 ` [PATCH 5/5] cpufreq: intel_pstate: Document the current behavior and user interface Rafael J. Wysocki
2017-03-30 21:01   ` [Update][PATCH v2 " Rafael J. Wysocki
2017-04-18 14:24     ` Rafael J. Wysocki [this message]
2017-05-05 21:38     ` [Resend][PATCH] " Rafael J. Wysocki
2017-05-12 20:47       ` Rafael J. Wysocki
2017-05-12 21:20         ` Jonathan Corbet
2017-05-12 21:42           ` Rafael J. Wysocki
2017-03-27  6:32 ` [PATCH 5/5] " Doug Smythies
2017-03-30  0:19   ` Rafael J. Wysocki

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=1603932.3tl1vUv8H6@aspire.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=corbet@lwn.net \
    --cc=dsmythies@telus.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=srinivas.pandruvada@linux.intel.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;
as well as URLs for NNTP newsgroup(s).