Ed Sweetman wrote:
Like i mentioned off list, the problem here is that cpu freq modules dont depend (Kconfig) on CONFIG_ACPI_PROCESSOR, yet they do.
Not really. Firstly, some of the cpufreq modules *do* depend on CONFIG_ACPI_PROCESSOR. Secondly, the ones that don't have an existing dependency do not actually depend on ACPI_PROCESSOR in some/most configurations.
I'll send in a patch to fix the real problem soon. Daniel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- [PATCH] Kconfig powernow-k8 driver should depend on ACPI P-States driver
- From: Joshua Hoblitt <[email protected]>
- Re: [PATCH] Kconfig powernow-k8 driver should depend on ACPI P-States driver
- From: Prakash Punnoor <[email protected]>
- Re: [PATCH] Kconfig powernow-k8 driver should depend on ACPI P-States driver
- From: "Duane Griffin" <[email protected]>
- Re: [PATCH] Kconfig powernow-k8 driver should depend on ACPI P-States driver
- From: Daniel Drake <[email protected]>
- Re: [PATCH] Kconfig powernow-k8 driver should depend on ACPI P-States driver
- From: Joshua Hoblitt <[email protected]>
- Re: [PATCH] Kconfig powernow-k8 driver should depend on ACPI P-States driver
- From: Ed Sweetman <[email protected]>
- [PATCH] Kconfig powernow-k8 driver should depend on ACPI P-States driver
- Prev by Date: Re: Why can't we sleep in an ISR?
- Next by Date: Re: 2.6.21-rc7: BUG: sleeping function called from invalid context at net/core/sock.c:1523
- Previous by thread: Re: [PATCH] Kconfig powernow-k8 driver should depend on ACPI P-States driver
- Next by thread: Re: [PATCH] Kconfig powernow-k8 driver should depend on ACPI P-States driver
- Index(es):