linux-kernel - Re: [PATCH 14/18] cpufreq: sh: move cpufreq driver to drivers/cpufreq

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: <CAKohpomqfVqiw1PJxBRRA8=A6hV_63AW4nRpM8TfZPA5bypcKQ@mail.gmail.com>
Date:	Tue, 9 Apr 2013 19:42:51 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	Simon Horman <horms@...ge.net.au>
Cc:	rjw@...k.pl, robin.randhawa@....com, Steve.Bannister@....com,
	Liviu.Dudau@....com, charles.garcia-tobin@....com,
	arvind.chauhan@....com, cpufreq@...r.kernel.org,
	linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
	linaro-kernel@...ts.linaro.org, patches@...aro.org,
	Paul Mundt <lethal@...ux-sh.org>, linux-sh@...r.kernel.org
Subject: Re: [PATCH 14/18] cpufreq: sh: move cpufreq driver to drivers/cpufreq

On 9 April 2013 18:25, Simon Horman <horms@...ge.net.au> wrote:
> On Thu, Apr 04, 2013 at 06:24:22PM +0530, Viresh Kumar wrote:
>> This patch moves cpufreq driver of SUPERH architecture to drivers/cpufreq.
>
> Why?
>
> I am missing the cover email where I assume the explanation lies.

Hi Simon,

The idea was to keep all cpufreq drivers at a common and most suitable
place, so that future consolidation work can be done easily and efficiently.

So, functionally this patch shouldn't change anything.
--
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/