Tags

This is the 3.4.65 stable release

This is the 3.0.99 stable release

ACPI and power management fixes for 3.12-rc4

 1) The resume part of user space driven hibernation (s2disk) is now
    broken after the change that moved the creation of memory bitmaps
    to after the freezing of tasks, because I forgot that the resume
    utility loaded the image before freezing tasks and needed the
    bitmaps for that.  The fix adds special handling for that case.

 2) One of recent commits changed the export of acpi_bus_get_device()
    to EXPORT_SYMBOL_GPL(), which was technically correct but broke
    existing binary modules using that function including one in
    particularly widespread use.  Change it back to EXPORT_SYMBOL().

 3) The intel_pstate driver sometimes fails to disable turbo if its
    no_turbo sysfs attribute is set.  Fix from Srinivas Pandruvada.

 4) One of recent cpufreq fixes forgot to update a check in cpufreq-cpu0
    which still (incorrectly) treats non-NULL as non-error.  Fix from
    Philipp Zabel.

 5) The SPEAr cpufreq driver uses a wrong variable type in one place
    preventing it from catching errors returned by one of the functions
    called by it.  Fix from Sachin Kamat.

/

IOMMU Fixes for Linux v3.12-rc3

A couple of fixes from the IOMMU side:

	* Some small fixes for the new ARM-SMMU driver
	* A register offset correction for VT-d
	* Adding MAINTAINERS entry for drivers/iommu

Overall no really big or intrusive changes.

This is the 3.11.3 stable release

This is the 3.10.14 stable release

This is the 3.4.64 stable release

This is the 3.0.98 stable release

Linux 3.12-rc3

ACPI and power management fixes for 3.12-rc3

 1) After recent locking changes in the cpufreq core it is possible
    to trigger BUG_ON(!policy) in lock_policy_rwsem_read() if
    cpufreq_get() is called before registering a cpufreq driver.
    Fix from Viresh Kumar.

 2) If intel_pstate has been loaded already, it doesn't make sense
    to do anything in acpi_cpufreq_init() and moreover doing something
    in there in that case may be harmful, so make that function return
    immediately if another cpufreq driver is already present.  From
    Yinghai Lu.

 3) The ACPI IPMI driver sometimes attempts to acquire a mutex from
    interrupt context, which can be avoided by replacing that mutex
    with a spinlock.  From Lv Zheng.

 4) A NULL pointer may be dereferenced by the exynos5440 cpufreq
    driver if a memory allocation made by it fails.  Fix from
    Sachin Kamat.

 5) Hanjun Guo's commit fixes a typo in the kerneldoc comment
    documenting acpi_bus_unregister_driver().

/

Small fbdev fixes for various fb drivers

This is the 3.11.2 stable release

This is the 3.10.13 stable release

This is the 3.4.63 stable release

This is the 3.0.97 stable release

Linux 3.12-rc2

ACPI and power management fixes for 3.12-rc2

 1) Four fixes for cpufreq regressions introduced by the changes that
    removed Device Tree parsing for CPU device nodes from cpufreq
    drivers from Sudeep KarkadaNagesha.

 2) Two fixes for recent cpufreq regressions introduced by changes
    related to the preservation of sysfs attributes over system
    suspend/resume cycles from Viresh Kumar.

 3) Fix for ACPI-based wakeup signaling in the PCI subsystem that
    fails to stop PME polling for devices put into the D3cold power
    state from Rafael J Wysocki.

 4) Fix for bad interactions between cpufreq and udev on systems
    supporting intel_pstate where acpi-cpufreq is available as well
    from Yinghai Lu.

/

Linux 3.12-rc1

This is the 3.11.1 stable release

This is the 3.10.12 stable release