[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130118162347.GA31499@srcf.ucam.org>
Date: Fri, 18 Jan 2013 16:23:47 +0000
From: Matthew Garrett <mjg59@...f.ucam.org>
To: Borislav Petkov <bp@...en8.de>,
"Gopalakrishnan, Aravind" <Aravind.Gopalakrishnan@....com>,
"rjw@...k.pl" <rjw@...k.pl>, Andre Przywara <andre@...rep.de>,
"cpufreq@...r.kernel.org" <cpufreq@...r.kernel.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Andreas <linuxuser330250@....net>
Subject: Re: [PATCH] drivers/cpufreq: Warn user when powernow-k8 tries to
fall back to acpi-cpufreq and it is unavailable.
On Thu, Jan 17, 2013 at 12:54:37PM +0100, Borislav Petkov wrote:
> So, handoff to acpi-cpufreq still has some issues. When both are
> built-in, the module_init functions turn into normal initcalls and
> in that case, they're executed in link order and it can happen that
> powernowk8_init() runs before acpi_cpufreq_init().
Just flip the link order? It's only the way it is because in the past we
wanted to try hardware-specific drivers before more generic ones, and I
don't think that's a concern in this case now.
--
Matthew Garrett | mjg59@...f.ucam.org
--
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/
Powered by blists - more mailing lists