linux-kernel - Re: [PATCH V3 2/2] cpufreq: Mark x86 drivers with CPUFREQ_SKIP_INITIAL_FREQ

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] [day] [month] [year] [list]

Date:	Fri, 29 Nov 2013 19:45:11 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	"Rafael J. Wysocki" <rjw@...ysocki.net>
Cc:	Lists linaro-kernel <linaro-kernel@...ts.linaro.org>,
	patches@...aro.org,
	"cpufreq@...r.kernel.org" <cpufreq@...r.kernel.org>,
	Linux PM list <linux-pm@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Nishanth Menon <nm@...com>, ceh@...com
Subject: Re: [PATCH V3 2/2] cpufreq: Mark x86 drivers with CPUFREQ_SKIP_INITIAL_FREQ_CHECK
 flag

On Fri, Nov 29, 2013 at 7:25 PM, Rafael J. Wysocki <rjw@...ysocki.net> wrote:
> I think you haven't missed any of them.
>
> That said, you need to do this in patch [1/2], or the kernel between
> patches [1/2] and [2/2] may be broken on some systems.
>
> If you want to do that in separate patches, the current [2/2] should be
> [1/2] and vice versa.
>
> I guess they will apply in the reverse order?

No, definition of CPUFREQ_SKIP_INITIAL_FREQ_CHECK would be
missing then after the first patch..

Anyway, I have fixed that and resent them now..
--
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/