linux-kernel - Re: [PATCH] cpufreq: governors: clean timer init and exit 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]

Date:	Thu, 31 Jan 2013 14:06:17 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Fabio Baltieri <fabio.baltieri@...aro.org>
Cc:	Viresh Kumar <viresh.kumar@...aro.org>, cpufreq@...r.kernel.org,
	linux-pm@...r.kernel.org, Linus Walleij <linus.walleij@...aro.org>,
	swarren@...dotorg.org, linaro-dev@...ts.linaro.org,
	Nicolas Pitre <nicolas.pitre@...aro.org>,
	mathieu.poirier@...aro.org, Joseph Lo <josephl@...dia.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] cpufreq: governors: clean timer init and exit code

On Thursday, January 31, 2013 12:06:13 PM Fabio Baltieri wrote:
> On Thu, Jan 31, 2013 at 04:23:06PM +0530, Viresh Kumar wrote:
> > On 30 January 2013 19:23, Fabio Baltieri <fabio.baltieri@...aro.org> wrote:
> > > Drop unused arguments from dbs_timer_init and clean dbs_timer_exit and
> > > cpufreq_governor_dbs to remove non necessary special cases.
> > >
> > > Reported-by: Viresh Kumar <viresh.kumar@...aro.org>
> > > Signed-off-by: Fabio Baltieri <fabio.baltieri@...aro.org>
> > 
> > As discussed over IRC, you will fix following in few days:
> > - Code redundancy within governors
> > - Removing second_time: label and cdbs->enable field
> > - Fixing params to timer init and exit to make them more efficient.
> 
> That's the plan, I'd leave it up to Rafael to decide if further cleanup
> patches should be included in 3.9 merge window or skip to the following
> one... I understand that we are starting to be late on the -rc and I
> also prefer to focus on fixup.

The deadline for 3.9 merge window patches is about 2 days before 3.8-rc7
(assuming that there will be -rc7) and by that time they need to be in
linux-next.  Whatever doesn't make it will have to go after 3.9-rc1 or be
postponed until the 3.10 merge window.

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