linux-kernel - Re: [PATCH] Documentation: cpu-freq: delete duplicate description of sysfs interface 'scaling

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]

Date:	Mon, 04 May 2015 23:27:49 +0200
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Wang Long <long.wanglong@...wei.com>
Cc:	corbet@....net, linux@...do.de, djwong@...ibm.com,
	viresh.kumar@...aro.org, linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org, peifeiyue@...wei.com,
	rafael.j.wysocki@...el.com
Subject: Re: [PATCH] Documentation: cpu-freq: delete duplicate description of sysfs interface 'scaling_driver'

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@...wei.com>

Can you please CC this one (and any future cpufreq patches) to
linux-pm@...r.kernel.org too?  It'll be easier to track it using Patchwork
then.


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/