[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2072518.dOpbznWpGj@vostro.rjw.lan>
Date: Tue, 22 Jan 2013 15:00:49 +0100
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Borislav Petkov <bp@...en8.de>
Cc: André Przywara <andre@...rep.de>,
Leonid Isaev <lisaev@...il.iu.edu>,
Tom Gundersen <teg@...m.no>, cpufreq@...r.kernel.org,
linux-acpi@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
Borislav Petkov <bp@...e.de>
Subject: Re: [PATCH 0/6] acpi-cpufreq and powernow-k8 fixes
On Sunday, January 20, 2013 11:24:24 AM Borislav Petkov wrote:
> From: Borislav Petkov <bp@...e.de>
>
> Hi all,
>
> here are a couple of patches fixing acpi-cpufreq and powernow-k8 loading
> sequence and handoff.
>
> Patch 0001 should be in Rafael's tree already but I'm adding it here for
> the sake of completeness. Basically, we want to address all possible
> cases of powernow-k8 and acpi-cpufreq:
>
> (M: module, Y: built-in)
>
> powernow-k8 acpi-cpufreq
> M M - powernow-k8 requests acpi-cpufreq
> M Y - powernow-k8 sees already loaded acpi-cpufreq
> Y M - impossible after patch 0001
> Y Y - patches 2,3 fix that
>
> Anyway, please take a look and let me know.
>
> Thanks.
>
>
>
>
> Borislav Petkov (5):
> powernow-k8: Add a kconfig dependency on acpi-cpufreq
> cpufreq: Make acpi-cpufreq link first
> cpufreq: Add a get_current_driver helper
> powernow-k8: Cleanup module request
> powernow-k8: Cleanup init function
>
> Matthew Garrett (1):
> acpi-cpufreq: Do not load on K8
Applied.
They are in linux-pm/bleeding-edge for now, I'll move them to linux-pm/linux-next
after build testing.
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/
Powered by blists - more mailing lists