linux-kernel - Re: [PATCH 2/2] cpufreq: governors: remove redundant code

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: <3245066.cWfgP9Ikey@vostro.rjw.lan>
Date:	Wed, 24 Oct 2012 23:12:13 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Viresh Kumar <viresh.kumar@...aro.org>
Cc:	cpufreq@...r.kernel.org, linux-pm@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linaro-dev@...ts.linaro.org, patches@...aro.org,
	pdsw-power-team@....com, arvind.chauhan@....com
Subject: Re: [PATCH 2/2] cpufreq: governors: remove redundant code

On Wednesday 24 of October 2012 21:43:46 Rafael J. Wysocki wrote:
> On Wednesday 24 of October 2012 11:37:13 Viresh Kumar wrote:
> > On 22 October 2012 14:16, Viresh Kumar <viresh.kumar@...aro.org> wrote:
> > > On 20 October 2012 01:42, Viresh Kumar <viresh.kumar@...aro.org> wrote:
> > >> Initially ondemand governor was written and then using its code conservative
> > >> governor is written. It used a lot of code from ondemand governor, but copy of
> > >> code was created instead of using the same routines from both governors. Which
> > >> increased code redundancy, which is difficult to manage.
> > >>
> > >> This patch is an attempt to move common part of both the governors to
> > >> cpufreq_governor.c file to come over above mentioned issues.
> > >>
> > >> This shouldn't change anything from functionality point of view.
> > >>
> > >> Signed-off-by: Viresh Kumar <viresh.kumar@...aro.org>
> > 
> > For everybody else, this patch is already pushed by Rafael in his linux-next
> > branch.
> 
> Well, not yet, although I'm going to do that.

Or I would if it still applied.  Unfortunately, though, it doesn't apply any
more to my linux-next branch due to some previous changes in it.

Care to rebase?

Rafael


-- 
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/