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] [day] [month] [year] [list]
Date:   Wed, 4 Jan 2017 23:34:24 +0100
From:   "Rafael J. Wysocki" <rafael@...nel.org>
To:     Jonathan Corbet <corbet@....net>
Cc:     "Rafael J. Wysocki" <rjw@...ysocki.net>,
        Viresh Kumar <viresh.kumar@...aro.org>,
        Shilpasri G Bhat <shilpa.bhat@...ux.vnet.ibm.com>,
        Linux PM <linux-pm@...r.kernel.org>,
        "open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Documentation: cpufreq: Update supported powernv processors

On Wed, Jan 4, 2017 at 11:20 PM, Jonathan Corbet <corbet@....net> wrote:
> 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. :)

Well, it actually is there in my linux-next branch and I was going to
include it in the next pull request.

Still, I can drop it easily enough. :-)

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

I can handle cpufreq docs updates, but if you think it's better to
route them via the docs tree, that would be fine by me too.

Thanks,
Rafael

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ