linux-kernel - Re: [Update][PATCH v2 5/5] cpufreq: intel_pstate: Document the current behavior and user interface

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1603932.3tl1vUv8H6@aspire.rjw.lan>
Date:   Tue, 18 Apr 2017 16:24:59 +0200
From:   "Rafael J. Wysocki" <rjw@...ysocki.net>
To:     Linux PM <linux-pm@...r.kernel.org>,
        Jonathan Corbet <corbet@....net>
Cc:     Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Doug Smythies <dsmythies@...us.net>
Subject: Re: [Update][PATCH v2 5/5] cpufreq: intel_pstate: Document the current behavior and user interface

Hi Jon,

On Thursday, March 30, 2017 11:01:48 PM Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@...el.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@...el.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