linux-kernel - Re: [PATCH 0/5] cpufreq: Fixes for 3.12

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: <1660632.57toTTMTf1@vostro.rjw.lan>
Date:	Tue, 20 Aug 2013 16:03:59 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Viresh Kumar <viresh.kumar@...aro.org>
Cc:	Lists linaro-kernel <linaro-kernel@...ts.linaro.org>,
	Patch Tracking <patches@...aro.org>,
	"cpufreq@...r.kernel.org" <cpufreq@...r.kernel.org>,
	"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/5] cpufreq: Fixes for 3.12

On Tuesday, August 20, 2013 06:07:14 PM Viresh Kumar wrote:
> On 20 August 2013 18:13, Rafael J. Wysocki <rjw@...k.pl> wrote:
> > Well, this looks good, but do we really need it in 3.12?  It doesn't look
> > like 3.12 will be missing these changes a lot?
> 
> Hmm.. If its too late for 3.12 we can skip them, but first two are bug
> fixes really (though nobody is affected as cpufreq_policy_list isn't used
> yet :) ) and other three are cleanups..
> 
> So, if there is any chance that we can queue them up for 3.12, it would
> be good.. but definitely not a must to have stuff. :)

OK, queued up for 3.12.  Hopefully, there won't be any fallout from [3/5].

Thanks,
Rafael

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