From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] Documentation: cpufreq: Update supported powernv
 processors
Date: Wed, 4 Jan 2017 15:20:51 -0700
Message-ID: <20170104152051.6bc78d04@lwn.net>
References: <1481887062-25522-1-git-send-email-shilpa.bhat@linux.vnet.ibm.com>
        <20170102070815.GB8588@vireshk-i7>
        <20170104143527.6193ee5f@lwn.net>
        <2779526.rqWzLUd9EW@aspire.rjw.lan>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
Return-path: <linux-doc-owner@vger.kernel.org>
In-Reply-To: <2779526.rqWzLUd9EW@aspire.rjw.lan>
Sender: linux-doc-owner@vger.kernel.org
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Viresh Kumar <viresh.kumar@linaro.org>, Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>, linux-pm@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
List-Id: linux-pm@vger.kernel.org

On Wed, 04 Jan 2017 23:11:30 +0100
"Rafael J. Wysocki" <rjw@rjwysocki.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