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  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, 10 Jul 2014 16:49:52 +0530
From:	Viresh Kumar <>
To:	Santosh Shilimkar <>
Cc:	"Rafael J. Wysocki" <>,
	Shawn Guo <>, Nishanth Menon <>,
	Lists linaro-kernel <>,
	"" <>,
	"" <>,
	Tomasz Figa <>,
	Stephen Boyd <>,
	Linux Kernel Mailing List <>,
	Thomas P Abraham <>,
	Arvind Chauhan <>,
	Sachin Kamat <>
Subject: Re: [PATCH 07/14] cpufreq: cpu0: OPPs can be populated at runtime

On 9 July 2014 20:14, Santosh Shilimkar <> wrote:
> Assuming you are updating bidnings as suggested by Stephen,
> patch looks good to me.
> Acked-by: Santosh Shilimkar <>

Why do you still have a separate cpufreq driver for omap?
Would this patch help getting that out?

I see this for omap:

static inline void omap_init_cpufreq(void)
        struct platform_device_info devinfo = { };

        if (!of_have_populated_dt())
       = "omap-cpufreq";
       = "cpufreq-generic";

and it makes me believe that you were just waiting for this patch?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists