Tags

This is the 2.6.32.62 stable release

This is the 3.2.59 stable release

This is the 3.4.91 stable release

ACPI and power management fixes for 3.15-rc6

 - ACPICA fix for a stale pointer access introduced by a recent
   commit in the XSDT validation code from Lv Zheng.

 - ACPICA fix for the default value of the command line switch
   to favor 32-bit FADT addresses (in case there's a conflict
   between a 64-bit and a 32-bit address).  The previous default
   was that the 32-bit version would take precedence and we tried
   to change it to the other way around and it didn't work.
   From Lv Zheng.

 - A TPM commit related to ACPI _DSM in 3.14 caused the driver to
   refuse to load if a specific _DSM was missing and that broke
   resume from system suspend on Chromebooks that require the TPM
   hardware to be restored to a working state during resume by the
   OS.  Restore the old behavior to load the driver if the _DSM
   in question is not present, but prevent it from using the
   feature the _DSM is for.

 - ACPI AC driver conversion in 3.13 broke thermal management on
   at least one machine and has to be reverted.  From Guenter Roeck.

 - Two reverts of 3.13 commits that attempted to remove the old ACPI
   battery interface in /proc, but turned out to break some utilities
   still using that interface.  From Lan Tianyu.

 - ACPI processor driver fix to prevent acpi_processor_add() from
   modifying the CPU device's .offline field which leads to breakage
   if the initial online of the CPU fails.  From Igor Mammedov.

 - Two intel_pstate fixes, one to take a BayTrail documentation update
   into account and one to avoid forcing the maximum P-state on init
   which causes CPU PM trouble on systems with P-states coordination
   when one of the CPU cores is initialized after an offline/online
   cycle triggered by user space.  Both stable candidates, from
   Dirk Brandewie.

 - Fix for the ACPI video DMI blacklist entry for Dell Inspiron 7520
   from Aaron Lu.

 - Two new ACPI video blacklist entries for machines shipping with
   Win8 that need to use native backlight so that it can be controlled
   in a usual way (which doesn't work otherwise due bugs in the ACPI
   tables) from Hans de Goede.

 - Two ACPI _OSI quirks for systems that need them to work correctly
   with Linux from Edward Lin and Hans de Goede.

/

This is the 3.12.20 stable release

This is the 3.4.90 stable release

This is the 3.10.40 stable release

This is the 3.14.4 stable release

Linux 3.15-rc5

This is the 3.12.19 stable release

This is the 3.14.3 stable release

This is the 3.10.39 stable release

This is the 3.4.89 stable release

- ring init improvements (Chris)
- vebox2 support (Zhao Yakui)
- more prep work for runtime pm on Baytrail (Imre)
- eDram support for BDW (Ben)
- prep work for userptr support (Chris)
- first parts of the encoder->mode_set callback removal (Daniel)
- 64b reloc fixes (Ben)
- first part of atomic plane updates (Ville)

Linux 3.15-rc4

ACPI and power management fixes for 3.15-rc4

 - There are two bugs in the ACPI PNP core that cause errors to
   be returned if optional ACPI methods are not present.  After
   an ACPI core change made in 3.14 one of those errors leads
   to serial port suspend failures on some systems.  Fix from
   Rafael J Wysocki.

 - A recently added PNP quirk related to Intel chipsets intorduced
   a build error in unusual configurations (PNP without PCI).  Fix
   from Bjorn Helgaas.

 - An ACPI EC workaround related to system suspend on Samsung machines
   added in 3.14 introduced a race causing some valid EC events to be
   discarded.  Fix from Kieran Clancy.

 - The acpi-cpufreq driver fails to load on some systems after a 3.14
   commit related to APIC ID parsing that overlooked one corner case.
   Fix from Lan Tianyu.

 - Fix for a recently introduced build problem in the ppc-corenet
   cpufreq driver from Tim Gardner.

 - A recent cpufreq core change to ensure serialization of frequency
   transitions for drivers with a ->target_index() callback overlooked
   the fact that some of those drivers had been doing operations
   introduced by it into the core already by themselves.  That resulted
   in a mess in which the core and the drivers try to do the same thing
   and block each other which leads to deadlocks.  Fixes for the
   powernow-k7, powernow-k6, and longhaul cpufreq drivers from
   Srivatsa S Bhat.

 - Fix for a computational error in the powernow-k6 cpufreq driver
   from Srivatsa S Bhat.

/

This is the 3.2.58 stable release