linux-kernel - Re: [PATCH] Documentation: cpufreq: Update supported powernv processors

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: <20170104152051.6bc78d04@lwn.net>
Date:   Wed, 4 Jan 2017 15:20:51 -0700
From:   Jonathan Corbet <corbet@....net>
To:     "Rafael J. Wysocki" <rjw@...ysocki.net>
Cc:     Viresh Kumar <viresh.kumar@...aro.org>,
        Shilpasri G Bhat <shilpa.bhat@...ux.vnet.ibm.com>,
        linux-pm@...r.kernel.org, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Documentation: cpufreq: Update supported powernv
 processors

On Wed, 04 Jan 2017 23:11:30 +0100
"Rafael J. Wysocki" <rjw@...ysocki.net> wrote:

> I'm assuming then, that you're going to handle cpufreq docs changes in the
> future.
> 
> Some cpufreq patches update the docs too, though, so there may be changes in
> there coming from two sources.

I saw it wasn't in linux-next yet, so figured I had to. :)

If you'd rather I stayed away from there, I'll happily do so, just say
the word (and preferably send a MAINTAINERS update :).

Thanks,

jon