From: "long.wanglong" <long.wanglong@huawei.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: <corbet@lwn.net>, <linux@brodo.de>, <djwong@us.ibm.com>,
<viresh.kumar@linaro.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <peifeiyue@huawei.com>,
<rafael.j.wysocki@intel.com>
Subject: Re: [PATCH] Documentation: cpu-freq: delete duplicate description of sysfs interface 'scaling_driver'
Date: Tue, 5 May 2015 09:19:52 +0800 [thread overview]
Message-ID: <55481AB8.5070604@huawei.com> (raw)
In-Reply-To: <2159903.qiTtABDclH@vostro.rjw.lan>
On 2015/5/5 5:27, Rafael J. Wysocki wrote:
> On Monday, May 04, 2015 09:16:58 AM Wang Long wrote:
>> The file 'Documentation/cpu-freq/user-guide.txt' has duplicate
>> description of sysfs interface 'scaling_driver'.
>>
>> [first]
>> scaling_driver : this file shows what cpufreq driver is
>> used to set the frequency on this CPU
>>
>> [second]
>> scaling_driver : Hardware driver for cpufreq.
>>
>> Although this does not affect anything, I think we should only have
>> one. so delete the second one because the first one is described in
>> more detail.
>>
>> Signed-off-by: Wang Long <long.wanglong@huawei.com>
>
> Can you please CC this one (and any future cpufreq patches) to
> linux-pm@vger.kernel.org too? It'll be easier to track it using Patchwork
> then.
>
>
OK, I will relay to this mail with CC the patch to linux-pm@vger.kernel.org.
next prev parent reply other threads:[~2015-05-05 1:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 9:16 [PATCH] Documentation: cpu-freq: delete duplicate description of sysfs interface 'scaling_driver' Wang Long
2015-05-04 10:38 ` Viresh Kumar
2015-05-04 21:27 ` Rafael J. Wysocki
2015-05-05 1:19 ` long.wanglong [this message]
2015-05-05 1:22 ` Wang Long
2015-05-15 0:24 ` 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=55481AB8.5070604@huawei.com \
--to=long.wanglong@huawei.com \
--cc=corbet@lwn.net \
--cc=djwong@us.ibm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
--cc=peifeiyue@huawei.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.org \
/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